All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Joe Thornber <thornber@redhat.com>,
	"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: convert dm-thin to use dm-bufio
Date: Fri, 19 Aug 2011 10:11:46 -0400	[thread overview]
Message-ID: <20110819141146.GC1335@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1108190926530.2592@hs20-bc2-1.build.redhat.com>

On Fri, Aug 19 2011 at  9:31am -0400,
Mikulas Patocka <mpatocka@redhat.com> wrote:

> On Fri, 19 Aug 2011, Mike Snitzer wrote:
> 
> > On Thu, Aug 18 2011 at  6:31pm -0400,
> > Mikulas Patocka <mpatocka@redhat.com> wrote:
> > 
> > > > This all sounds good; get the locking interface in and I'll switch to
> > > > bufio straight away.
> > > > 
> > > > - Joe
> > > 
> > > I uploaded bufio-based block manager at 
> > > http://people.redhat.com/mpatocka/patches/kernel/dm-thinp-bufio/. It 
> > > supports locks, but it defines new functions down_write_non_owner and 
> > > up_write_non_owner.
> > 
> > dm-bufio.patch:
> > drivers/md/Kconfig needs a more comprehensive description for DM_BUFIO's
> > help.
> 
> There is intentionally no description. If there is no description, this 
> option won't appear in "make menuconfig" menu.
> 
> dm-bufio is selected automatically when some module that needs it is 
> configured. There is no need to select dm-bufio manually.

Hmm, I wonder if it makes sense to remove DM_PERSISTENT_DATA's help
description?

(we already select DM_PERSISTENT_DATA when DM_THIN_PROVISIONING is
selected -- but it is visible in menuconfig because it has a
description).

  reply	other threads:[~2011-08-19 14:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 20:18 [PATCHES] convert dm-thin to use dm-bufio Mikulas Patocka
2011-08-15  9:04 ` Joe Thornber
2011-08-15 18:26   ` Mikulas Patocka
2011-08-16  9:16     ` Joe Thornber
2011-08-16 22:03       ` Mikulas Patocka
2011-08-17  8:26         ` Joe Thornber
2011-08-18 22:31           ` Mikulas Patocka
2011-08-19  7:04             ` Mike Snitzer
2011-08-19  9:11               ` Joe Thornber
2011-08-19  9:46                 ` Mike Snitzer
2011-08-19 10:17                   ` Mike Snitzer
2011-08-19 10:22                   ` Joe Thornber
2011-08-19 13:49                     ` Mike Snitzer
2011-08-19 14:11                       ` Alasdair G Kergon
2011-08-19 13:31               ` Mikulas Patocka
2011-08-19 14:11                 ` Mike Snitzer [this message]
2011-08-19 15:37                 ` Joe Thornber
2011-08-19 18:25                   ` Mike Snitzer
2011-08-19 18:50                     ` Alasdair G Kergon
2011-08-19  9:12             ` [PATCHES] " Joe Thornber
2011-08-19 16:17               ` Joe Thornber
2011-08-20  1:10                 ` [PATCH 1/2] dm bufio: fix "value computed is not used" warnings Mike Snitzer
2011-08-20  1:10                   ` [PATCH 2/2] dm space map: only include bitops.h in dm-space-map-common.c Mike Snitzer
2011-08-22 13:29                   ` [PATCH 1/2] dm bufio: fix "value computed is not used" warnings Mikulas Patocka
2011-08-22 18:24                 ` [PATCHES] convert dm-thin to use dm-bufio Mikulas Patocka
2011-08-22 19:59                   ` Mikulas Patocka
2011-08-23 11:23                     ` Joe Thornber

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=20110819141146.GC1335@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=thornber@redhat.com \
    /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.