linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Bill Speirs <bill.speirs@gmail.com>
Cc: Rob Landley <rob@landley.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Userspace Block Device
Date: Tue, 19 May 2015 16:19:02 +0100	[thread overview]
Message-ID: <20150519161902.10881f9b@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CAB_f4-UNx68COuxO+TkTKY_A9+Vu+agnvOrnSWJpktWO5LdTdg@mail.gmail.com>

> - Write an ndb-server that is essentially a gateway between nbd and
> S3/Google. For each nbd request, I translate it into the appropriate
> S3/Google request and respond appropriately.
> - I'd run the above server on the machine on some port.
> - I'd run a client on the same server using 127.0.0.1 and the above
> port, providing the nbd block device.
> - Go drink a beer as I rack up a huge bill with Amazon or Google

And you probably would because the block layer will see a lot of I/O
requests that you would really want to process locally, as well as stuff
caused by working at the block not file level (like readaheads).

You also can't deal with coherency this way - eg sharing the virtual disk
between two systems because the file system code isn't expecting other
clients to modify the disk under it.

Rather than nbd you could also look at drbd or some similar kind of
setup where you keep the entire filestore locally and write back changes
to the remote copy. As you can never share the filestore when mounted you
can cache it pretty aggressively.

Alan

  reply	other threads:[~2015-05-19 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 19:01 Userspace Block Device Bill Speirs
2015-05-19  5:34 ` Rob Landley
2015-05-19 14:42   ` Bill Speirs
2015-05-19 15:19     ` One Thousand Gnomes [this message]
2015-05-19 15:33       ` Bill Speirs

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=20150519161902.10881f9b@lxorguk.ukuu.org.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=bill.speirs@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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).