xen-devel
[Xen-devel] Re: Too many I/O controller patches
To: |
s-uchida@xxxxxxxxxxxxx |
Subject: |
[Xen-devel] Re: Too many I/O controller patches |
From: |
Hirokazu Takahashi <taka@xxxxxxxxxxxxx> |
Date: |
Tue, 05 Aug 2008 21:01:50 +0900 (JST) |
Cc: |
xen-devel@xxxxxxxxxxxxxxxxxxx, containers@xxxxxxxxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, dave@xxxxxxxxxxxxxxxxxx, vtaras@xxxxxxxxxx, dm-devel@xxxxxxxxxx, agk@xxxxxxxxxxxxxx, ryov@xxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, ngupta@xxxxxxxxxx, righi.andrea@xxxxxxxxx |
Delivery-date: |
Tue, 05 Aug 2008 05:02:17 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<000901c8f6a5$fe64ba30$fb2e2e90$@jp.nec.com> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<1217870433.20260.101.camel@nimitz> <489748E6.5080106@xxxxxxxxx> <000901c8f6a5$fe64ba30$fb2e2e90$@jp.nec.com> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Hi,
> I think that OOM problems caused by memory/cache systems.
> So, it will be better that I/O controller created out of these problems
> first, although a lateness of the I/O device would be related.
> If these problem can be resolved, its technique should be applied into
> normal I/O control as well as cgroups.
Yes, this is one of the problems linux kernel still has, which should
be solved.
But I believe this should be done in the linux memory management layer
including the cgroup memory controller, which has to work correctly
on any type of device with various access speeds.
I think it's better that I/O controllers should only focus on flow of
I/O requests. This approach will keep the implementation of linux
kernel simple.
> Buffered write I/O is also related with cache system.
> We must consider this problem as I/O control.
> I don't have a good way which can resolve this problems.
>
Thank you,
Hirokazu Takahashi.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH 5/7] bio-cgroup: Remove a lot of ifdefs, (continued)
- Message not available
- [Xen-devel] Re: [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts, Hirokazu Takahashi
- Message not available
- [Xen-devel] Re: [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts, Hirokazu Takahashi
- Message not available
- Message not available
- [Xen-devel] Re: [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts, Hirokazu Takahashi
- Message not available
- [Xen-devel] Re: [PATCH 4/7] bio-cgroup: Split the cgroup memory subsystem into two parts, Hirokazu Takahashi
- Message not available
- Message not available
- [Xen-devel] RE: Too many I/O controller patches, Satoshi UCHIDA
- [Xen-devel] Re: Too many I/O controller patches,
Hirokazu Takahashi <=
- Message not available
- [Xen-devel] Re: Too many I/O controller patches, Ryo Tsuruta
- Message not available
- Message not available
- [Xen-devel] Re: RFC: I/O bandwidth controller, Ryo Tsuruta
- Message not available
- Message not available
- [Xen-devel] RE: I/O bandwidth controller (was Re: Too many I/O controllerpatches), Caitlin Bestler
- Message not available
- Message not available
- [Xen-devel] Re: RFC: I/O bandwidth controller, Hirokazu Takahashi
- [Xen-devel] Re: RFC: I/O bandwidth controller, Ryo Tsuruta
- Message not available
- [Xen-devel] Re: RFC: I/O bandwidth controller, Ryo Tsuruta
- [Xen-devel] Re: RFC: I/O bandwidth controller, Hirokazu Takahashi
[Xen-devel] [PATCH 0/7] I/O bandwidth controller and BIO tracking, Ryo Tsuruta
|
|
|