From: Josef Bacik <josef@toxicpanda.com>
To: Bart Van Assche <bvanassche@acm.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Christoph Hellwig <hch@infradead.org>
Cc: 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@kernel.org, dm-devel@redhat.com,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
agk@redhat.com, Mike Christie <michael.christie@oracle.com>
Subject: Re: [dm-devel] [PATCH v1 0/5] dm: dm-user: New target that proxies BIOs to userspace
Date: Thu, 10 Dec 2020 12:03:21 -0500 [thread overview]
Message-ID: <30d39293-80a4-9ef5-92bb-6b6dec464be3@toxicpanda.com> (raw)
In-Reply-To: <6fb5be2d-c6ca-c21b-dddf-9b314973dcfe@acm.org>
On 12/9/20 10:38 PM, Bart Van Assche wrote:
> On 12/7/20 10:55 AM, Palmer Dabbelt wrote:
>> All in all, I've found it a bit hard to figure out what sort of interest
>> people
>> have in dm-user: when I bring this up I seem to run into people who've done
>> similar things before and are vaguely interested, but certainly nobody is
>> chomping at the bit. I'm sending it out in this early state to try and
>> figure
>> out if it's interesting enough to keep going.
>
> Cc-ing Josef and Mike since their nbd contributions make me wonder
> whether this new driver could be useful to their use cases?
>
Sorry gmail+imap sucks and I can't get my email client to get at the original
thread. However here is my take.
1) The advantages of using dm-user of NBD that you listed aren't actually
problems for NBD. We have NBD working in production where you can hand off the
sockets for the server without ending in timeouts, it was actually the main
reason we wrote our own server so we could use the FD transfer stuff to restart
the server without impacting any clients that had the device in use.
2) The extra copy is a big deal, in fact we already have too many copies in our
existing NBD setup and are actively looking for ways to avoid those.
Don't take this as I don't think dm-user is a good idea, but I think at the very
least it should start with the very best we have to offer, starting with as few
copies as possible.
If you are using it currently in production then cool, there's clearly a usecase
for it. Personally as I get older and grouchier I want less things in the
kernel, so if this enables us to eventually do everything NBD related in
userspace with no performance drop then I'd be down. I don't think you need to
make that your primary goal, but at least polishing this up so it could
potentially be abused in the future would make it more compelling for merging.
Thanks,
Josef
next prev parent reply other threads:[~2020-12-10 17:04 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 [this message]
2020-12-15 3:00 ` Palmer Dabbelt
2020-12-16 18:24 ` Vitaly Mayatskih
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=30d39293-80a4-9ef5-92bb-6b6dec464be3@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=agk@redhat.com \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--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).