Linux bcache driver list
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor-KvP5wT2u2U0@public.gmane.org>
To: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: Piergiorgio Sartor
	<piergiorgio.sartor-KvP5wT2u2U0@public.gmane.org>,
	Adam Berkan <aberkan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Formatting of backing device
Date: Thu, 2 Feb 2012 23:24:31 +0100	[thread overview]
Message-ID: <20120202222431.GA7171@lazy.lzy> (raw)
In-Reply-To: <20120202221101.GA26768-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>

Hi Kent,

nice to have you in this discussion!

> > I understand that the actual implementation is easier and,
> > maybe, simpler, since a completely new device is added,
> > which will have the new caching "features", while the
> > old one (backing device) is just a further layer.
> > This is similar to LVM over md over /dev/sdX.
> 
> The reason for getting rid of transparent caching didn't have anything
> to do with ease of implementation: the real reason is that safely doing
> persistent caching (and writeback!) is impossible with transparent
> caching.

Well, it seems to me "impossible" is a big word...
I could image is more "invasive".

> Adding back a mode that caches a device without a bcache superblock but
> without the cache being persistent isn't out of the question, but it

I miss the point, the superblock can be stored in
the caching device, instead of the backing and
the actual device *could* stay the same.
The kernel would have to discover first the caching,
later the backing and then put things together.
So, the cache will be persistent, or?

As I wrote above, I see this more complex than
adding a further layer, likely I would do the same.

> wouldn't be terribly useful to us so it's not at all a priority for me.
> If someone else wrote the code I'd take patches, though.

No time for that, unfortunately.

I take the opportunity to congratulate personally
to you for this project, well done!

bye,

-- 

piergiorgio

  parent reply	other threads:[~2012-02-02 22:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 10:10 Formatting of backing device Piergiorgio Sartor
     [not found] ` <20120201101041.GA2779-W+Wf6LxwHt0@public.gmane.org>
2012-02-01 19:12   ` Adam Berkan
     [not found] ` <CAHYUNGYcs3CeRA8Pk-R_3hA6mFHshKzysxRaCcsfm3WLT__B0A@mail.gmail.com>
     [not found]   ` <CAHYUNGYcs3CeRA8Pk-R_3hA6mFHshKzysxRaCcsfm3WLT__B0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 20:54     ` Piergiorgio Sartor
     [not found]       ` <20120201205456.GA7669-W+Wf6LxwHt0@public.gmane.org>
2012-02-01 21:43         ` Adam Berkan
     [not found]       ` <CAHYUNGaB4LCESDWU1tWB1ZJp_kBH_=19e07vCndxXS5T98_xBA@mail.gmail.com>
     [not found]         ` <CAHYUNGaB4LCESDWU1tWB1ZJp_kBH_=19e07vCndxXS5T98_xBA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 21:44           ` Piergiorgio Sartor
     [not found]             ` <20120201214443.GA8544-W+Wf6LxwHt0@public.gmane.org>
2012-02-01 23:11               ` Adam Berkan
2012-02-02 19:01                 ` Piergiorgio Sartor
     [not found]                   ` <20120202190122.GA2353-W+Wf6LxwHt0@public.gmane.org>
2012-02-02 22:11                     ` Kent Overstreet
     [not found]                       ` <20120202221101.GA26768-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-02-02 22:24                         ` Piergiorgio Sartor [this message]
2012-02-16 19:42                           ` Alex Elsayed
     [not found]                             ` <loom.20120216T200235-190-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2012-02-16 20:33                               ` Piergiorgio Sartor
     [not found]                                 ` <20120216203332.GA6597-W+Wf6LxwHt0@public.gmane.org>
2012-02-16 20:50                                   ` Alex Elsayed
     [not found]                                     ` <CA++fp8wcxTDJ=mbsKmWi27+yRZg-tyNdWgmhWU6=UeWgC0TZuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-16 20:52                                       ` Alex Elsayed
2012-02-16 22:35                                       ` Piergiorgio Sartor
     [not found]                                         ` <20120216223554.GA6947-W+Wf6LxwHt0@public.gmane.org>
2012-02-16 23:09                                           ` Joseph Glanville
     [not found]                                             ` <CAOzFzEhO+6ECN-WjvtMK+-2g7Dwo+DPwQMVWuCZG=Y3BVRNEBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-16 23:17                                               ` Piergiorgio Sartor
     [not found]                                                 ` <20120216231754.GA14206-W+Wf6LxwHt0@public.gmane.org>
2012-02-16 23:34                                                   ` Alex Elsayed
     [not found]                                                     ` <CA++fp8w7_uUd35Tcwy1bwEYpR6tJ+fkWMEg+iVEyJ1H4hqKBKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-16 23:35                                                       ` Alex Elsayed
2012-02-17 19:12                                                       ` Piergiorgio Sartor

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=20120202222431.GA7171@lazy.lzy \
    --to=piergiorgio.sartor-kvp5wt2u2u0@public.gmane.org \
    --cc=aberkan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox