From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Emmanuel Lacour <elacour@easter-eggs.com>,
kvm@vger.kernel.org
Subject: Re: Using tools such as ionice inside guests
Date: Thu, 19 May 2016 22:12:20 +0200 [thread overview]
Message-ID: <573E1E24.6090506@de.ibm.com> (raw)
In-Reply-To: <1fc1093d-b77a-c56f-80ba-0b58f151f4a7@redhat.com>
On 05/18/2016 07:12 PM, Paolo Bonzini wrote:
>
>
> On 18/05/2016 18:26, Emmanuel Lacour wrote:
>> Thanks, it's a bad news for us :(
>>
>> I will try to play with cgroups io throttling to limit by iops or bytes
>> read, but it'll be a hard limit rather than a priority :(
>
> That probably won't work either, but you can use io throttling on the
> host too.
>
>> Do you think there could be back some io priority throttling in not so
>> far future kernels?
>
> I wouldn't oppose a patch to add back the non-mq path, but as far as I
> know nobody is working on it. It's not hard and I can help if you need
> guidance.
>
> Adding I/O scheduler support to blk-mq has been promised for at least a
> year now, but I'm not aware of which kernel release might have the work.
> It's not even been submitted to LKML, so I guess it's quite far away.
What actually happened to the virtio-blk multiqueue support in QEMU?
next prev parent reply other threads:[~2016-05-19 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 15:49 Using tools such as ionice inside guests Emmanuel Lacour
2016-05-18 16:13 ` Paolo Bonzini
2016-05-18 16:26 ` Emmanuel Lacour
2016-05-18 17:12 ` Paolo Bonzini
2016-05-19 20:12 ` Christian Borntraeger [this message]
2016-05-20 10:35 ` Paolo Bonzini
2016-05-20 12:54 ` Emmanuel Lacour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=573E1E24.6090506@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=elacour@easter-eggs.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox