From: Pavel Machek <pavel@ucw.cz>
To: Theodore Ts'o <tytso@mit.edu>,
Reindl Harald <h.reindl@thelounge.net>,
linux-ext4@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
kent.overstreet@gmail.com, linux-bcache@vger.kernel.org
Subject: Re: bcache with existing ext4 filesystem
Date: Mon, 24 Jul 2017 22:04:51 +0200 [thread overview]
Message-ID: <20170724200451.GA4318@amd> (raw)
In-Reply-To: <20170724192718.t7n5zgualz5lillg@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
Hi!
On Mon 2017-07-24 15:27:18, Theodore Ts'o wrote:
> On Mon, Jul 24, 2017 at 09:15:48PM +0200, Pavel Machek wrote:
> > >
> > > Am 24.07.2017 um 20:57 schrieb Pavel Machek:
> > > >Would it be feasible to run bcache (write-through) with existing ext4
> > > >filesystem?
> > > >
> > > >I have 400GB of data I'd rather not move, and SSD I could use for
> > > >caching. Ok, SSD is connecte over USB2, but I guess it is still way
> > > >faster then seeking harddrive on random access
> > >
> > > i doubt that seriously - USB2 has a terrible latency
> >
> > Well.. if that's too slow, I can get SSD M.2; plus bcache docs says
> > that combination works.
> >
> > And... if you ever tried to do git diff while git checkout is running
> > on spinning rust... spinning rust has awful parameters when idle, and
> > it only gets worse when loaded :-(.
>
> So some hard numbers. Max throughput of USB 2.0 is 53 MiB/s[1]. In
> actual practice the max throughput you will see out of the USB 2.0
> interface is 30-40 MiB/s. In contrast, a HDD doing sequential reads
> can easily do much more than that.
>
> [1] https://superuser.com/questions/317217/whats-the-maximum-typical-speed-possible-with-a-usb2-0-drive
>
> So a lot is going to depend on how bcache works. If you can get large
> sequential reads and writes to *bypass* the cache device, then I think
> there's a good cache that bcache on a USB 2.0 device won't hurt. It
> might not help as much as you like, but that's a function of the
> overhead of populating the cache and whether the cache can keep the
> useful bits in the cache device.
Another useful number is that spinning rust does less than 3MB/sec on
common operations done by git. (Yes, probably because a lot of
seeking). So... USB device should be able to help.
Question for you was... Is the first 1KiB of each ext4 filesystem still
free and "reserved for a bootloader"?
If I needed more for bcache superblock (8KiB, IIRC), would that be
easy to accomplish on existing filesystem?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-07-24 20:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 18:57 bcache with existing ext4 filesystem Pavel Machek
2017-07-24 19:08 ` Reindl Harald
2017-07-24 19:15 ` Pavel Machek
2017-07-24 19:27 ` Theodore Ts'o
2017-07-24 20:04 ` Pavel Machek [this message]
2017-07-25 4:51 ` Theodore Ts'o
2017-07-25 6:43 ` Pavel Machek
2017-07-25 10:32 ` Vojtech Pavlik
2017-07-25 11:12 ` Pavel Machek
2017-07-25 16:10 ` Theodore Ts'o
2017-07-25 18:13 ` Eric Wheeler
2017-07-25 22:02 ` Pavel Machek
2017-07-26 17:41 ` Eric Wheeler
2017-07-26 18:59 ` Austin S. Hemmelgarn
2017-07-26 19:16 ` Eric Wheeler
2017-07-26 20:01 ` Pavel Machek
2017-07-25 13:46 ` Pavel Machek
2017-07-25 18:02 ` Theodore Ts'o
2017-07-25 20:55 ` Pavel Machek
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=20170724200451.GA4318@amd \
--to=pavel@ucw.cz \
--cc=h.reindl@thelounge.net \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).