From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK aio examples
Date: Fri, 17 Jun 2016 17:24:47 +0000 [thread overview]
Message-ID: <1466184287.26925.81.camel@intel.com> (raw)
In-Reply-To: B4C78186-D836-4BB4-988C-44985BEBC049@playstation.sony.com
[-- Attachment #1: Type: text/plain, Size: 2737 bytes --]
On Wed, 2016-06-15 at 23:56 +0000, Bhadauria, Varun wrote:
> Hello Ben
>
> Thank you for the clarification. I was under the false impression that Linux AIO can be made to
> use SPDK under the hood which is clearly not the case since they will have to go through the
> filesystem.
I'm sure someone could wrap the AIO interface around the SPDK driver for the specific case where the
user is opening a block device directly with O_DIRECT. It's nearly a 1:1 translation for that case.
Unfortunately, most people use Linux AIO on files instead of block devices.
> BTW are there any known early filesystem implementation besides ceph’s rocksdb based bluestore FS
> which use SPDK.
The only publicly announced one that I'm aware of is Bluestore inside of Ceph. As long as SPDK
continues to be valuable, I fully expect many filesystems with different designs to appear over
time. If you have a particular use case where you'd like some sort of filesystem-like layer on top
of SPDK, I'd love to hear about it. At a minimum, it's useful to collect requirements from a number
of sources.
>
> Regards,
> Varun Bhadauria
>
>
> On 6/15/16, 4:37 PM, "SPDK on behalf of Walker, Benjamin" <spdk-bounces(a)lists.01.org on behalf of
> benjamin.walker(a)intel.com> wrote:
>
> >
> > Can you explain a bit more about why you want to use AIO? Are you referring to Linux AIO or
> > POSIX AIO? If you want to do a performance comparison of Linux AIO and the SPDK NVMe driver then
> > the perf tool is your best bet.
> >
> > You can run the perf tool against a block device using Linux AIO by binding your NVMe device to
> > the kernel ("./scripts/setup.sh reset" will hand them all back to the kernel) and then doing
> > something like:
> >
> > ./perf -q 1 -s 4096 -w read -t 10 /dev/nvme0n1 /dev/nvme1n1
> >
> > -----Original Message-----
> > From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Bhadauria, Varun
> > Sent: Wednesday, June 15, 2016 4:30 PM
> > To: Storage Performance Development Kit <spdk(a)lists.01.org>
> > Subject: [SPDK] SPDK air examples
> >
> > Hello
> >
> > Are there any SPDK examples which use AIO? Perf.c has very little documentation in the usage
> > for AIO.
> >
> > Regards,
> > Varun Bhadauria
> >
> >
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2016-06-17 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 17:24 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-22 17:35 [SPDK] SPDK aio examples Walker, Benjamin
2016-06-22 16:50 Bhadauria, Varun
2016-06-17 21:57 Walker, Benjamin
2016-06-17 20:52 Bhadauria, Varun
2016-06-15 23:56 Bhadauria, Varun
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=1466184287.26925.81.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.