Dominik Klein wrote:
> Hi
>
> back with some testing results.
>
>>> how about the start Guest with option "cache=none" to bypass pagecache?
>>> This should help i think.
>> I will read up on where to set that and give it a try. Thanks for the hint.
>
> So here's what I did and found out:
>
> Th
Ahh, sure.
Dominik Klein wrote:
>> Please add "oflag=direct" to see how it goes.
>
> Any objections on continuing this discussion in thread "blkio cgroup"
> where Vivek Goyal, the blkio controller author, replied to my posting?
>
> I'm in the middle of answering his questions there.
>
> Regards
> Please add "oflag=direct" to see how it goes.
Any objections on continuing this discussion in thread "blkio cgroup"
where Vivek Goyal, the blkio controller author, replied to my posting?
I'm in the middle of answering his questions there.
Regards
Dominik
--
libvir-list mailing list
libvir-lis
Hi
back with some testing results.
>> how about the start Guest with option "cache=none" to bypass pagecache?
>> This should help i think.
>
> I will read up on where to set that and give it a try. Thanks for the hint.
So here's what I did and found out:
The host system has 2 12 core CPUs and
Gui Jianfeng wrote:
> Igor Serebryany wrote:
>> On Fri, Feb 18, 2011 at 04:12:28PM +0800, Gui Jianfeng wrote:
>>> "blkio.weight" is used to control the Minimal Maximal Bandwidth. If you'd
>>> like
>>> to control Max bandwidth to let your guests become I/O hungery.
>>> "blkio.throttle.*"
>>> shoul
Hi
I can only comment on some of your questions as I also can't say to
understand this completely.
> Then, blkio.throttle can be used to set actual hard limits on IO
> consumption -- like, no more than 10Mbps for this VM. I can already do
> this with blkio cgroups, but just not from libvirt -- ye
Igor Serebryany wrote:
> On Fri, Feb 18, 2011 at 04:12:28PM +0800, Gui Jianfeng wrote:
>> "blkio.weight" is used to control the Minimal Maximal Bandwidth. If you'd
>> like
>> to control Max bandwidth to let your guests become I/O hungery.
>> "blkio.throttle.*"
>> should helps. But these tunables
>> As far as I understand, and as far as I saw during my tests, the blkio
>> controller only works for sync I/O requests (eg dd with oflag=direct).
>> Buffered I/O is not part of the control.
>
> Yes, you are right.
whew :)
>> And since a VM's I/O is most likely buffered in some fashion, this do
Dominik Klein wrote:
>> Hmm.. "blkio.weight" is used to control the Minimal Maximal Bandwidth. If
>> you'd like
>> to control Max bandwidth to let your guests become I/O hungery.
>> "blkio.throttle.*"
>> should helps. But these tunables aren't supported by blkiotune for the time
>> being.
>> I'm
On Fri, Feb 18, 2011 at 04:12:28PM +0800, Gui Jianfeng wrote:
> "blkio.weight" is used to control the Minimal Maximal Bandwidth. If you'd like
> to control Max bandwidth to let your guests become I/O hungery.
> "blkio.throttle.*"
> should helps. But these tunables aren't supported by blkiotune for
> Hmm.. "blkio.weight" is used to control the Minimal Maximal Bandwidth. If
> you'd like
> to control Max bandwidth to let your guests become I/O hungery.
> "blkio.throttle.*"
> should helps. But these tunables aren't supported by blkiotune for the time
> being.
> I'm considering to implement th
Dominik Klein wrote:
> Hi Gui,
>
> thanks for your reply.
>
>> Actually, this two series doesn't care how blkio cgroup works. They just
>> provide
>> the ability to put Guest into given cgroup and tune the tunables.
>> Currently, You can only control the "blkio.weight" tunable. For examle, If
>
Hi Gui,
thanks for your reply.
> Actually, this two series doesn't care how blkio cgroup works. They just
> provide
> the ability to put Guest into given cgroup and tune the tunables.
> Currently, You can only control the "blkio.weight" tunable. For examle, If
> you'd
> like to give more I/O ba
Dominik Klein wrote:
> Hi
>
> not that I tested this patch or the patch that followed (adding
> blkiotune command) ... but the way I understand, the cgroup blkio
> controller does only work for sync'd IO/queues.
>
> quote blkio-controller.txt from 2.6.37:
> Currently only sync IO queues are suppo
Hi
not that I tested this patch or the patch that followed (adding
blkiotune command) ... but the way I understand, the cgroup blkio
controller does only work for sync'd IO/queues.
quote blkio-controller.txt from 2.6.37:
Currently only sync IO queues are support. All the buffered writes are
sti
Eric Blake wrote:
> On 02/07/2011 11:38 PM, Gui Jianfeng wrote:
>> Hi
>>
>> This patchset adds blkio cgroup support for qemu and lxc.
>>
>> [PATCH 1/6] cgroup: Enable cgroup hierarchy for blkio cgroup
>> [PATCH 2/6 v3] cgroup: Implement blkio.weight tuning API.
>> [PATCH 3/6] Update XML Schema for
On 02/07/2011 11:38 PM, Gui Jianfeng wrote:
> Hi
>
> This patchset adds blkio cgroup support for qemu and lxc.
>
> [PATCH 1/6] cgroup: Enable cgroup hierarchy for blkio cgroup
> [PATCH 2/6 v3] cgroup: Implement blkio.weight tuning API.
> [PATCH 3/6] Update XML Schema for new entries.
> [PATCH 4/6
Hi
This patchset adds blkio cgroup support for qemu and lxc.
[PATCH 1/6] cgroup: Enable cgroup hierarchy for blkio cgroup
[PATCH 2/6 v3] cgroup: Implement blkio.weight tuning API.
[PATCH 3/6] Update XML Schema for new entries.
[PATCH 4/6 v3] qemu: Implement blkio tunable XML configuration and par
18 matches
Mail list logo
