| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: RFC: I/O bandwidth controller
|
To: |
fernando@xxxxxxxxxxxxx |
|
Subject: |
[Xen-devel] Re: RFC: I/O bandwidth controller |
|
From: |
Hirokazu Takahashi <taka@xxxxxxxxxxxxx> |
|
Date: |
Fri, 08 Aug 2008 20:39:44 +0900 (JST) |
|
Cc: |
xen-devel@xxxxxxxxxxxxxxxxxxx, uchida@xxxxxxxxxxxxx, containers@xxxxxxxxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, dm-devel@xxxxxxxxxx, righi.andrea@xxxxxxxxx, agk@xxxxxxxxxxxxxx, dave@xxxxxxxxxxxxxxxxxx, ngupta@xxxxxxxxxx, balbir@xxxxxxxxxxxxxxxxxx |
|
Delivery-date: |
Fri, 08 Aug 2008 04:40:10 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<1218078075.3803.149.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
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: |
<1217985189.3154.57.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4899D464.1070506@xxxxxxxxxxxxxxxxxx> <1218078075.3803.149.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Hi,
> > Would you like to split up IO into read and write IO. We know that read can
> > be
> > very latency sensitive when compared to writes. Should we consider them
> > separately in the RFC?
> Oops, I somehow ended up leaving your first question unanswered. Sorry.
>
> I do not think we should consider them separately, as long as there is a
> proper IO tracking infrastructure in place. As you mentioned, reads can
> be very latecy sensitive, but the read case could be treated as an
> special case IO controller/IO tracking subsystem. There certainly are
> optimization opportunities. For example, in the synchronous I/O patch ww
> could mark bios with the iocontext of the current task, because it will
> happen to be originator of that IO. By effectively caching the ownership
> information in the bio we can avoid all the accesses to struct page,
> page_cgroup, etc, and reads would definitively benefit from that.
FYI, we should also take special care of pages being reclaimed, the free
memory of the cgroup these pages belong to may be really low.
Dm-ioband is doing this.
Thanks,
Hirokazu Takahashi.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home