From: Kent Overstreet <kent.overstreet@gmail.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: zab@zabbo.net, linux-bcache@vger.kernel.org, rickyb@google.com,
mrubin@google.com, sviatoslavpestov@gmail.com,
adam.berkan@gmail.com
Subject: Re: [ANNOUNCE] bcachefs!
Date: Tue, 14 Jul 2015 01:11:05 -0700 [thread overview]
Message-ID: <20150714081105.GA18569@kmo-pixel> (raw)
In-Reply-To: <CACaajQtwx45r8GcRmchrQwDts1GH-V8g0x1FwGfDvnfm02bq+Q@mail.gmail.com>
On Tue, Jul 14, 2015 at 09:05:39AM +0300, Vasiliy Tolstov wrote:
> Does it support discards?
Yes
> Does this announce means that bcache block device
> no longer maintained by developers?
There's no plural, it's just me :)
I've been overly stressed and burned out from a startup gone horribly wrong -
I'm going to try to start doing some maintainence of upstream bcache again once
I've moved.
I apologize for my absence on the list these past months, I've had (and still
have) entirely too much to juggle - hint hint, if anyone wants to jump in and
help out.
> What about performance tests with compared to plain btrfs/ext4?
I haven't done much comparison benchmarking yet, I'll post them once I have. If
anyone else wants to do some benchmarking I'd love to see the results.
(From the testing I have done - untarring the kernel (on a fast device, with the
tar file already uncompressed and in kernel so we're purely cpu bound) -
bcachefs is equal to ext4 to within the margin of error. On dbench when we're
purely cpu bound, bcachefs is roughly 30% off from ext4. I think the majority of
that is bcachefs's dirent code being somewhat cpu heavy).
The long term goal is to be at least as fast on ext4/xfs for any given workload,
and on typical workloads we ought to be faster - and in particular bcachefs
should have better and more predictable latency, due to the way journalling
works.
> Format command have one device, how provide tiering?
--tier specifies the tier of the devices that come after it, where the smaller
index is the faster tier.
Only tiers 0 and 1 are supported for now, that will be increased whenever
someone gets around to it.
If /dev/sda is your fast device and /dev/sdb is your slow device, run
# bcacheadm format -C /dev/sda --tier 1 /dev/sdb
bcacheadm format --help gives you the full list of options.
> 14 июля 2015 г. 3:58 пользователь "Kent Overstreet" <
> kent.overstreet@gmail.com> написал:
>
> > Short announcement, because I'm in the process of moving - but I wanted to
> > get
> > this out there because the code is up and I think it's reasonably stable
> > right
> > now.
> >
> > Bcachefs is a posix filesystem that I've been working towards for - well,
> > quite
> > awhile now: it's intended as a competitor/replacement for ext4/xfs/btrfs.
> >
> > Current features
> > - multiple devices
> > - replication
> > - tiering
> > - data checksumming and compression (zlib only; also the code doesn't
> > work with
> > tiering yet)
> > - most of the normal posix fs features (no fallocate or quotas yet)
> >
> > Planned features:
> > - snapshots!
> > - erasure coding
> > - more
> >
> > There will be a longer announcement on LKML/linux-fs in the near future
> > (after
> > I'm finished moving) - but I'd like to get it a bit more testing from a
> > wider
> > audience first, if possible.
> >
> > You need the bcache-dev branch, and the new bcache tools - be warned, this
> > code
> > is _not_ compatible with the upstream bcache on disk format:
> >
> > $ git clone -b bcache-dev http://evilpiepirate.org/git/linux-bcache.git
> > $ git clone -b dev http://evilpiepirate.org/git/bcache-tools.git
> >
> > Then do the usual compiling...
> >
> > # bcacheadm format -C /dev/sda1
> > # mount /dev/sda1 /mnt
> >
> > The usual caveats apply - it might eat your data, the on disk format has
> > _not_
> > been stabilized yet, etc. But it's been reasonably stable for me, and
> > passes all
> > but 2-3 of the supported xfstests.
> >
> > Try it out and let me know how it goes!
> >
> > Also, programmers please check out the bcache guide - feedback is
> > appreciated:
> >
> > http://bcache.evilpiepirate.org/BcacheGuide/
> >
> > Thanks!
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
next prev parent reply other threads:[~2015-07-14 8:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 0:58 [ANNOUNCE] bcachefs! Kent Overstreet
[not found] ` <CACaajQtwx45r8GcRmchrQwDts1GH-V8g0x1FwGfDvnfm02bq+Q@mail.gmail.com>
2015-07-14 8:11 ` Kent Overstreet [this message]
2015-07-20 1:11 ` Denis Bychkov
[not found] ` <CAC7rs0uWSt85F443PRw1zvybccg+EfebaSyH9EhUwHjhTGryRA@mail.gmail.com>
[not found] ` <CAC7rs0upqkuH1CPd-OAmrpQ=8PmaDpzHYY1MaBDpAL6TS_iKyw@mail.gmail.com>
2015-07-20 2:52 ` Denis Bychkov
2015-07-24 19:25 ` Kent Overstreet
2015-07-15 6:11 ` Ming Lin
[not found] ` <CAC7rs0sbg2ci6=niQ0X11AONZbr2AOYhRbxfDH_w4N4A7dyPLw@mail.gmail.com>
2015-07-15 7:15 ` Ming Lin
2015-07-15 7:39 ` Ming Lin
2015-07-17 23:17 ` Kent Overstreet
2015-07-17 23:35 ` Ming Lin
2015-07-17 23:40 ` Kent Overstreet
2015-07-17 23:48 ` Ming Lin
2015-07-17 23:51 ` Kent Overstreet
2015-07-17 23:58 ` Ming Lin
2015-07-18 2:10 ` Kent Overstreet
2015-07-18 5:21 ` Ming Lin
2015-07-22 5:11 ` Ming Lin
2015-07-22 5:15 ` Ming Lin
2015-07-24 19:15 ` Kent Overstreet
2015-07-24 20:47 ` Ming Lin
2015-07-28 18:41 ` Ming Lin
2015-07-28 18:45 ` Ming Lin
2015-08-06 6:40 ` Ming Lin
2015-08-06 23:11 ` Kent Overstreet
2015-08-07 5:21 ` Ming Lin
2015-08-06 22:58 ` Kent Overstreet
2015-08-06 23:27 ` Ming Lin
2015-08-06 23:59 ` Kent Overstreet
2015-07-18 0:01 ` Denis Bychkov
2015-07-18 2:12 ` Kent Overstreet
2015-07-19 7:46 ` Denis Bychkov
2015-07-21 18:37 ` David Mohr
2015-07-21 21:53 ` Jason Warr
2015-07-24 19:32 ` Kent Overstreet
2015-07-24 19:42 ` Jason Warr
2015-07-22 7:19 ` Killian De Volder
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=20150714081105.GA18569@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=adam.berkan@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=mrubin@google.com \
--cc=rickyb@google.com \
--cc=sviatoslavpestov@gmail.com \
--cc=v.tolstov@selfip.ru \
--cc=zab@zabbo.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 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.