From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Dongli Zhang <dongli.zhang@oracle.com>,
Cornelia Huck <cohuck@redhat.com>,
mst@redhat.com, virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, axboe@kernel.dk,
linux-kernel@vger.kernel.org
Subject: Re: virtio-blk: should num_vqs be limited by num_possible_cpus()?
Date: Thu, 21 Mar 2019 15:57:46 +0000 [thread overview]
Message-ID: <20190321155746.GE31434@stefanha-x1.localdomain> (raw)
In-Reply-To: <f92a5ef9-04b9-d6fa-a7f8-c855a87cd0fb@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Wed, Mar 20, 2019 at 08:53:33PM +0800, Jason Wang wrote:
>
> On 2019/3/19 上午10:22, Dongli Zhang wrote:
> > Hi Jason,
> >
> > On 3/18/19 3:47 PM, Jason Wang wrote:
> > > On 2019/3/15 下午8:41, Cornelia Huck wrote:
> > > > On Fri, 15 Mar 2019 12:50:11 +0800
> > > > Jason Wang <jasowang@redhat.com> wrote:
> > option 3:
> > We should allow more vectors even the block layer would support at most
> > nr_cpu_ids queues.
> >
> >
> > I understand a new policy for queue-vector mapping is very helpful. I am just
> > asking the question from block layer's point of view.
> >
> > Thank you very much!
> >
> > Dongli Zhang
>
>
> Don't know much for block, cc Stefan for more idea.
Thanks for CCing me. I don't have much input at this stage.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2019-03-21 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:22 Dongli Zhang
2019-03-12 17:33 ` Cornelia Huck
2019-03-13 3:26 ` Dongli Zhang
2019-03-13 9:39 ` Cornelia Huck
2019-03-14 6:12 ` Dongli Zhang
2019-03-14 12:13 ` Cornelia Huck
2019-03-14 16:08 ` Dongli Zhang
2019-03-15 4:50 ` Jason Wang
2019-03-15 12:41 ` Cornelia Huck
2019-03-18 7:47 ` Jason Wang
2019-03-19 2:22 ` Dongli Zhang
2019-03-20 12:53 ` Jason Wang
2019-03-21 2:14 ` Dongli Zhang
2019-03-21 15:57 ` Stefan Hajnoczi [this message]
2019-03-14 12:32 ` Michael S. Tsirkin
2019-03-14 15:36 ` Dongli Zhang
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=20190321155746.GE31434@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=axboe@kernel.dk \
--cc=cohuck@redhat.com \
--cc=dongli.zhang@oracle.com \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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
all inboxes | Powered by JetHome®