From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Slava Pestov <sp@datera.io>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Using vmalloc instead of get_free_pages?
Date: Mon, 29 Dec 2014 10:06:14 +0100 [thread overview]
Message-ID: <20141229090614.GA521@cuci.nl> (raw)
In-Reply-To: <CACHGV4LPBS1Y-9ciKBpPGeeF9yuF9zfPySYbBSM12m6s+8VmDw@mail.gmail.com>
Slava Pestov wrote:
>On Sat, Dec 27, 2014 at 2:52 AM, Stephen R. van den Berg <srb@cuci.nl> wrote:
>> - That the amount of memory being allocated for a single caching device
>> exceeds maximum the amount allocatable by get_free_pages(), so I changed
>As you've already noticed this is fixed in bcache-dev, but that brings in a
I already hoped it would have been, but since the ondisk format changed,
I couldn't fully confirm this yet. I don't mind changing the on-disk format,
BTW, because I am still able to reformat the disks before the servers
go into production.
>Support for multiple cache devices is in bcache-dev, it requires changes
>to both make-bcache and the kernel. I'm not sure what the time frame for
>upstreaming this is, since the changes are more involved.
Well, I don't mind running a custom kernel and custom bcache userspace
tools for a while. I have been rolling my own kernels since 1992.
I presume that eventually all changes will be upstreamed (including the
changes in the on-disk format)? So, until then, I'll simply rebase bcache-dev
on top of the most recent kernels manually.
I *would* be interested in the new bcache userspace tools though then.
--
Stephen.
prev parent reply other threads:[~2014-12-29 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 10:52 Using vmalloc instead of get_free_pages? Stephen R. van den Berg
2014-12-29 4:09 ` Slava Pestov
2014-12-29 9:06 ` Stephen R. van den Berg [this message]
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=20141229090614.GA521@cuci.nl \
--to=srb@cuci.nl \
--cc=linux-bcache@vger.kernel.org \
--cc=sp@datera.io \
/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