spdk.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
* [SPDK] 回复: About single virtio-blk device performance
@ 2022-10-14  3:18 Bin Yang
  0 siblings, 0 replies; only message in thread
From: Bin Yang @ 2022-10-14  3:18 UTC (permalink / raw)
  To: spdk

[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]

Hi Changpeng:
      Thanks for your reply!
      Will community accept the commits as using multiple cores for a virtio-blk device?
      If not,  what are the main concerns?

________________________________
发件人: Liu, Changpeng <changpeng.liu(a)intel.com>
发送时间: 2022年10月13日 15:16
收件人: Storage Performance Development Kit <spdk(a)lists.01.org>
主题: [SPDK] Re: About single virtio-blk device performance

Hi Bin Yang,

I think that's the only benefit by using multiple cores for a virtio-blk device, if your tests case is for a VM,
Actually you can add multiple devices to this VM.


> -----Original Message-----
> From: Bin Yang <bin.yang(a)jaguarmicro.com>
> Sent: Wednesday, October 12, 2022 3:02 PM
> To: spdk(a)lists.01.org
> Subject: [SPDK] About single virtio-blk device performance
>
> Hello, Everyone!
>
>     For spdk vhost_blk,can we distribute multi queues requests in different cpu
> to improve single virtio-blk device performance?
> for example,create request poller for each queue and distribute the pollers in
> different threads.  Does this feasible?
>
> Thanks!
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-10-14  3:18 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-14  3:18 [SPDK] 回复: About single virtio-blk device performance Bin Yang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).