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>,
	linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache on layered devices
Date: Tue, 7 Feb 2012 20:12:13 +0100	[thread overview]
Message-ID: <20120207191213.GA2581@lazy.lzy> (raw)
In-Reply-To: <CAH+dOxKir2mKZfq6r=aHngQeRxmPreS9=ch4dGaFtGscfkxBpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Kent,

thanks for the answer.

Reading bcache docs, I found that there should be
distinction, in bcache, between "small" writes
and "large" writes.

I was wondering if the choice of the layer could
influence this distinction.
Namely, LV uses PE of 4MB, which, I'm not sure,
results in writes of 4MB as smallest size.

Thanks,

bye,

pg

On Mon, Feb 06, 2012 at 12:34:57PM -0800, Kent Overstreet wrote:
> I'd personally use the raid as the backing device but any would work -
> you would have duplicates ending up in the cache if you cached the
> hard drives directly.
> 
> On Mon, Feb 6, 2012 at 10:56 AM, Piergiorgio Sartor
> <piergiorgio.sartor-KvP5wT2u2U0@public.gmane.org> wrote:
> > Hi all again,
> >
> > I'm not sure if the topic was already discussed here,
> > anyway I'll go ahead, sorry if it is a duplication.
> >
> > I was wondering, in case of layered devices, what would
> > be the best layer to use as backing device.
> >
> > Specifically, I've two HDDs in RAID10 (Linux md driver,
> > software RAID), on top of the RAID there are LV partitions.
> >
> > Obviously, it would be possible to use the RAID components,
> > i.e. the HDDs as backing devices, or the RAID itself, or
> > the LV partitions (/dev/mapper/VolXXX).
> >
> > My guess would be to use the LV partitions, since these
> > are closer to the filesystem, but, maybe, using the RAID
> > or even the single HDDs could be better.
> >
> > Any idea on the topic? Suggestions & motivations?
> >
> > Thanks a lot in advance,
> >
> > bye,
> >
> > --
> >
> > piergiorgio
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

piergiorgio

      parent reply	other threads:[~2012-02-07 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 18:56 bcache on layered devices Piergiorgio Sartor
     [not found] ` <20120206185612.GA2381-W+Wf6LxwHt0@public.gmane.org>
2012-02-06 20:34   ` Kent Overstreet
     [not found]     ` <CAH+dOxKir2mKZfq6r=aHngQeRxmPreS9=ch4dGaFtGscfkxBpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-07 19:12       ` Piergiorgio Sartor [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=20120207191213.GA2581@lazy.lzy \
    --to=piergiorgio.sartor-kvp5wt2u2u0@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