All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Any idea for SPDK to limit the data transfer speed
Date: Mon, 08 May 2017 17:00:34 +0000	[thread overview]
Message-ID: <1494262832.3021.19.camel@intel.com> (raw)
In-Reply-To: 20170507071713.5F9DD10200E6@webmail.sinamail.sina.com.cn

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

On Sun, 2017-05-07 at 15:17 +0800, nixun_992(a)sina.com wrote:
> 
>      For one nvme device, if i config SPDK with two partitions, is there any
> way to limit the transfer speed to a fix speed? I know the kernel has cgroup
> limit and buffered io limit, if i want to implement this in SPDK, is there a
> way to archive this?
> 

As Changpeng said, we don't have any quality of service code in SPDK today
(patches welcome). However, we do have a vision for where that type of code
would go. We expect this type of thing to be implemented as a bdev module
(lib/bdev). Specifically, a virtual bdev that is layered on top of the other
physical bdevs. That way, the same code can be used for all of the different
types of backing storage. We have one example of how to write a virtual bdev
(lib/bdev/split) which is a simple splitter that you can use to get started.

Note that the community is currently doing some major refactoring on the bdev
layer in preparation for stabilizing and "finalizing" the API of this component.
The big changes coming do the following things:

1) Use the env wrapper instead of calling DPDK directly
2) Remove the dependency on the event framework (lib/event)
3) Full support for zero copy read and write, where possible*
4) Documentation!

*This is only possible with appropriate hardware support

Thanks,
Ben

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]

             reply	other threads:[~2017-05-08 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 17:00 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-08  6:30 [SPDK] Any idea for SPDK to limit the data transfer speed Liu, Changpeng
2017-05-08  3:28 nixun_992
2017-05-07 16:49 Luse, Paul E
2017-05-07  7:17 nixun_992

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=1494262832.3021.19.camel@intel.com \
    --to=spdk@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.