From: Christoph Hellwig <hch@infradead.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: dm-devel@redhat.com, agk@redhat.com, snitzer@redhat.com,
corbet@lwn.net, song@kernel.org,
Palmer Dabbelt <palmerdabbelt@google.com>,
shuah@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-kselftest@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v1 0/5] dm: dm-user: New target that proxies BIOs to userspace
Date: Fri, 4 Dec 2020 10:33:36 +0000 [thread overview]
Message-ID: <20201204103336.GA7374@infradead.org> (raw)
In-Reply-To: <20201203215859.2719888-1-palmer@dabbelt.com>
What is the advantage over simply using nbd?
next prev parent reply other threads:[~2020-12-04 10:34 UTC|newest]
Thread overview: 19+ 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 ` Christoph Hellwig [this message]
2020-12-07 18:55 ` [PATCH v1 0/5] dm: dm-user: New target that proxies BIOs to userspace 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
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
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=20201204103336.GA7374@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=corbet@lwn.net \
--cc=dm-devel@redhat.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=palmer@dabbelt.com \
--cc=palmerdabbelt@google.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).