From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: Neil Brown <neilb@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: userspace block driver?
Date: Wed, 09 Nov 2005 03:01:42 -0500 [thread overview]
Message-ID: <4371ACE6.7010503@pobox.com> (raw)
In-Reply-To: <20051109075455.GN3699@suse.de>
Jens Axboe wrote:
> On Wed, Nov 09 2005, Jeff Garzik wrote:
>
>>Neil Brown wrote:
>>
>>>On Wednesday November 9, jgarzik@pobox.com wrote:
>>>
>>>
>>>>Has anybody put any thought towards how a userspace block driver
>>>>would work?
>>>
>>>
>>>Isn't this was enbd does?
>>> http://www.it.uc3m.es/~ptb/nbd/
>>
>>Is there something there relevant for modern kernels? I would sure hope
>>I could come up with something more lightweight than that.
>
>
> I was going to say drbd, but then you did say more lightweight :-)
>
> Is nbd completely screwed these days?
nbd does more than I want.
_All_ that is needed is flipping requests <somehow> to/from userspace.
nbd messes directly with sockets and such, which I don't want. It does
way too much, hardcodes way too much.
loop is a closer model to a generic userspace block device than nbd, I
think.
Though, answering your question directly, I do get the impression that
in-kernel nbd has been left behind in favor of drbd and enbd, out in the
few places where nbd-ish solutions are used.
Jeff
next prev parent reply other threads:[~2005-11-09 8:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 7:27 userspace block driver? Jeff Garzik
2005-11-09 7:37 ` Neil Brown
2005-11-09 7:46 ` Jeff Garzik
2005-11-09 7:54 ` Jens Axboe
2005-11-09 8:01 ` Jeff Garzik [this message]
2005-11-09 12:42 ` Paulo Marques
2005-11-09 12:54 ` Miklos Szeredi
2005-11-09 14:04 ` Miklos Szeredi
2005-11-11 0:12 ` Andrew Morton
2005-11-11 5:59 ` Miklos Szeredi
2005-11-09 10:12 ` Lars Marowsky-Bree
2005-11-09 7:50 ` Chris Wright
2005-11-09 7:55 ` Oliver Neukum
2005-11-09 8:37 ` Avi Kivity
2005-11-09 13:32 ` Jonathan Corbet
2005-11-09 20:56 ` Guennadi Liakhovetski
2005-11-12 23:42 ` Guennadi Liakhovetski
2005-11-10 13:13 ` Pavel Machek
2005-11-16 3:13 ` Michael Clark
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=4371ACE6.7010503@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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