public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Zachary Amsden <zamsden@redhat.com>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	axboe@kernel.dk, hch@infradead.org, akpm@linux-foundation.org,
	Paul.Clements@steeleye.com, tytso@mit.edu,
	miklos <miklos@szeredi.hu>
Subject: Re: [PATCH] Allow userspace block device implementation
Date: Tue, 28 Jul 2009 10:21:31 +0900	[thread overview]
Message-ID: <4A6E529B.9030104@kernel.org> (raw)
In-Reply-To: <20090727142536.465799aa@lxorguk.ukuu.org.uk>

Hello,

Alan Cox wrote:
>> Somehow this made me think of FUSE/CUSE... should this be named aBUSE?
>> Oh wait it is :-), what I'm after is I guess is, can we share some of
>> the FUSE/CUSE code?
> 
> It reminds me of the existing and perfectly functional network block
> device (nbd) we already have and which has also been present for years.

Yeah, I think this is the biggest hurdle against (a)BUSE.  Is it
sufficiently different from nbd?  nbd-like functionality can be
implemented something via FUSE and maybe it can be said that things
are cleaner that way but nbd has been in the kernel for a long time
now and it's definitely much easier to do swap over it when the whole
thing is in kernel.

Thanks.

-- 
tejun

  parent reply	other threads:[~2009-07-28  1:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27  9:57 [PATCH] Allow userspace block device implementation Zachary Amsden
2009-07-27 12:56 ` Peter Zijlstra
2009-07-27 13:25   ` Alan Cox
2009-07-27 19:46     ` Zachary Amsden
2009-07-27 20:24       ` Peter Zijlstra
2009-07-27 21:02       ` Alan Cox
2009-07-28  1:21     ` Tejun Heo [this message]
2009-07-28  3:53       ` Zachary Amsden
2009-07-28 10:27         ` Alan Cox
2009-07-28 16:00           ` Linus Torvalds
2009-07-28 18:36             ` Kyle Moffett
2009-07-28 18:51               ` Linus Torvalds
2009-07-28 19:07               ` Alan Cox
2009-07-28 19:49               ` Andi Kleen
2009-07-28 20:50                 ` Linus Torvalds
2009-07-28 21:09                   ` Andi Kleen
2009-07-28 22:56                   ` Theodore Tso
2009-08-07 18:08 ` Pavel Machek
2009-08-10 22:47   ` Zachary Amsden
  -- strict thread matches above, loose matches on Subject: below --
2009-07-28 20:37 devzero

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=4A6E529B.9030104@kernel.org \
    --to=tj@kernel.org \
    --cc=Paul.Clements@steeleye.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=zamsden@redhat.com \
    /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