From: Robert White <rwhite@pobox.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: NOCOW and Swap Files?
Date: Wed, 22 Oct 2014 13:39:58 -0700 [thread overview]
Message-ID: <5448161E.6020306@pobox.com> (raw)
In-Reply-To: <20141022202519.GC18164@carfax.org.uk>
On 10/22/2014 01:25 PM, Hugo Mills wrote:
> The new code is the swap-on-NFS infrastructure, which indirects
> swapfile accesses through the filesystem code. The reason you have to
> do that with NFS is because NFS doesn't expose a block device at all,
> so you can't get a list of blocks on an underlying device because
> there isn't one. Indirecting the accesses through the filesystem,
> however, allows us to side-step btrfs's problems with part (b) above,
> and in theory gives us swapfile capability.
I was not even aware there was "new code" on the matter.
Is there a guide or whatever to doing this? I didn't see any mention of
it in the places Google led me.
--Rob
next prev parent reply other threads:[~2014-10-22 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 20:08 NOCOW and Swap Files? Robert White
2014-10-22 20:25 ` Hugo Mills
2014-10-22 20:39 ` Robert White [this message]
2014-10-22 20:42 ` Hugo Mills
2014-10-22 20:48 ` Robert White
2014-10-23 7:34 ` Russell Coker
2014-10-23 11:22 ` Austin S Hemmelgarn
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=5448161E.6020306@pobox.com \
--to=rwhite@pobox.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.