From: Josef Bacik <josef@toxicpanda.com>
To: Wouter Verhelst <w@uter.be>
Cc: Josef Bacik <josef@toxicpanda.com>,
Roman Stratiienko <roman.stratiienko@globallogic.com>,
linux-kernel@vger.kernel.org, nbd@other.debian.org,
Aleksandr Bulyshchenko <A.Bulyshchenko@globallogic.com>,
linux-block@vger.kernel.org, axboe@kernel.dkn.org
Subject: Re: [PATCH 2/2] nbd: add support for nbd as root device
Date: Fri, 14 Jun 2019 09:38:04 -0400 [thread overview]
Message-ID: <20190614133802.vg3w3sxpid2fpbp4@MacBook-Pro-91.local> (raw)
In-Reply-To: <20190614103343.GB11340@grep.be>
On Fri, Jun 14, 2019 at 12:33:43PM +0200, Wouter Verhelst wrote:
> On Thu, Jun 13, 2019 at 10:55:36AM -0400, Josef Bacik wrote:
> > Also I mean that there are a bunch of different nbd servers out there. We have
> > our own here at Facebook, qemu has one, IIRC there's a ceph one.
>
> I can't claim to know about the Facebook one of course, but the qemu one
> uses the same handshake protocol as anyone else. The ceph ones that I've
> seen do too (but there are various implementations of that, so...).
>
Ah, for some reason I remembered Qemu's being distinctly different.
I suppose if most of the main ones people use are using the same handshake
protocol that makes it more compelling. But there'd have to be a really good
reason why a initramfs isn't viable, and so far I haven't heard a solid reason
that's not an option other than "it's hard and we don't want to do it."
> > They all have their own connection protocols. The beauty of NBD is
> > that it doesn't have to know about that part, it just does the block
> > device part, and I'd really rather leave it that way. Thanks,
>
> Sure.
>
> OTOH, there is definitely also a benefit to using the same handshake
> protocol everywhere, for interoperability reasons.
>
Sure, Facebook's isn't different because we hate the protocol, we just use
Thrift for all of our services, and thus it makes sense for us to use thrift for
the client connection stuff to make it easy on all the apps that use disagg.
Thanks,
Josef
next prev parent reply other threads:[~2019-06-14 13:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 16:31 [PATCH 1/2] nbd: make sock_xmit() and nbd_add_socket() more generic roman.stratiienko
2019-06-12 16:31 ` [PATCH 2/2] nbd: add support for nbd as root device roman.stratiienko
2019-06-13 12:56 ` Eric Blake
2019-06-13 13:02 ` Eric Blake
2019-06-13 13:14 ` Eric Blake
2019-06-13 13:52 ` Josef Bacik
2019-06-13 14:45 ` Roman Stratiienko
2019-06-13 14:55 ` Josef Bacik
2019-06-13 16:21 ` Roman Stratiienko
2019-06-13 16:54 ` Josef Bacik
2019-06-14 10:33 ` Wouter Verhelst
2019-06-14 13:38 ` Josef Bacik [this message]
2019-06-14 21:23 ` Wouter Verhelst
2019-06-13 15:14 ` Eric Blake
2019-06-13 16:05 ` Roman Stratiienko
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=20190614133802.vg3w3sxpid2fpbp4@MacBook-Pro-91.local \
--to=josef@toxicpanda.com \
--cc=A.Bulyshchenko@globallogic.com \
--cc=axboe@kernel.dkn.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=roman.stratiienko@globallogic.com \
--cc=w@uter.be \
/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).