From: Vitaly Mayatskih <v.mayatskih@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: josef@toxicpanda.com, bvanassche@acm.org,
Christoph Hellwig <hch@infradead.org>,
Mike Snitzer <snitzer@redhat.com>,
corbet@lwn.net, kernel-team@android.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, Song Liu <song@kernel.org>,
dm-devel@redhat.com, linux-kselftest@vger.kernel.org,
shuah@kernel.org, agk@redhat.com, michael.christie@oracle.com
Subject: Re: [dm-devel] [PATCH v1 0/5] dm: dm-user: New target that proxies BIOs to userspace
Date: Wed, 16 Dec 2020 13:24:59 -0500 [thread overview]
Message-ID: <CAGF4SLgDvS7VOih4XZ+sqx6jVK3wBQZan+uZMVsdYdVEPZdrpw@mail.gmail.com> (raw)
In-Reply-To: <mhng-2da5b1a2-20f9-4b0e-9ffd-7f60a161ebf0@palmerdabbelt-glaptop>
On Mon, Dec 14, 2020 at 10:03 PM Palmer Dabbelt <palmer@dabbelt.com> wrote:
> I was really experting someone to say that. It does seem kind of silly to build
> out the new interface, but not go all the way to a ring buffer. We just didn't
> really have any way to justify the extra complexity as our use cases aren't
> that high performance. I kind of like to have benchmarks for this sort of
> thing, though, and I didn't have anyone who had bothered avoiding the last copy
> to compare against.
I worked on something very similar, though performance was one of the
goals. The implementation was floating around lockless ring buffers,
shared memory for zerocopy, multiqueue and error handling. It could be
that every disk storage vendor has to implement something like that in
order to bridge Linux kernel to their own proprietary datapath running
in userspace.
--
wbr, Vitaly
next prev parent reply other threads:[~2020-12-16 18:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 21:58 [PATCH v1 0/5] dm: dm-user: New target that proxies BIOs to userspace Palmer Dabbelt
2020-12-03 21:58 ` [PATCH v1 1/5] Documentation: Describe dm-user Palmer Dabbelt
2020-12-03 21:58 ` [PATCH v1 2/5] uapi: Add dm-user structure definition Palmer Dabbelt
2020-12-03 21:58 ` [PATCH v1 3/5] dm: dm-user: New target that proxies BIOs to userspace Palmer Dabbelt
2020-12-03 21:58 ` [PATCH v1 4/5] selftests/dm-user: A handful of tests for dm-user Palmer Dabbelt
2020-12-03 21:58 ` [PATCH v1 5/5] MAINTAINERS: Add myself as a dm-user maintainer Palmer Dabbelt
2020-12-04 10:33 ` [PATCH v1 0/5] dm: dm-user: New target that proxies BIOs to userspace Christoph Hellwig
2020-12-07 18:55 ` Palmer Dabbelt
2020-12-10 3:38 ` [dm-devel] " Bart Van Assche
2020-12-10 17:03 ` Josef Bacik
2020-12-15 3:00 ` Palmer Dabbelt
2020-12-16 18:24 ` Vitaly Mayatskih [this message]
2020-12-17 6:55 ` Palmer Dabbelt
2020-12-22 13:32 ` Christoph Hellwig
2020-12-22 14:36 ` Mike Snitzer
2020-12-22 20:38 ` Palmer Dabbelt
2020-12-23 7:48 ` Christoph Hellwig
2020-12-23 16:59 ` Bart Van Assche
2020-12-22 20:31 ` [dm-devel] " Palmer Dabbelt
[not found] <CABmKtjfdDS-iO+jLkwt7x-oDHt9V1p-cpYHjL5EV2NKwHxqN1Q@mail.gmail.com>
2020-12-16 20:35 ` Palmer Dabbelt
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=CAGF4SLgDvS7VOih4XZ+sqx6jVK3wBQZan+uZMVsdYdVEPZdrpw@mail.gmail.com \
--to=v.mayatskih@gmail.com \
--cc=agk@redhat.com \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=palmer@dabbelt.com \
--cc=shuah@kernel.org \
--cc=snitzer@redhat.com \
--cc=song@kernel.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;
as well as URLs for NNTP newsgroup(s).