public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Karel Zak <kzak@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>,
	mbroz@redhat.com, agk@redhat.com
Subject: Re: [PATCH] blkid: optimize dm_device_is_leaf() usage
Date: Wed, 27 Aug 2008 01:26:43 -0600	[thread overview]
Message-ID: <20080827072643.GT3392@webber.adilger.int> (raw)
In-Reply-To: <20080827001942.GN6029@nb.net.home>

On Aug 27, 2008  02:19 +0200, Karel Zak wrote:
> On Tue, Aug 26, 2008 at 07:32:25PM -0400, Theodore Tso wrote:
> > you'll just be re-inventing blkid.  If you don't cache, you'll either
> 
>  Hehe.. I will directly copy code from blkid and vol_id. It's open
>  source. I needn't re-inventing ;-)

Couldn't you just change libblkid to export the probe functions?  It
always makes me cringe when code like this is copied, because I just
_know_ one or the other will become out of date, and it will take
twice as much effort to keep them in sync.  I'd rather see people
doing "high value" work instead of watching for and copying patches
around.

> > Or maybe the right answer is /proc/partitions should only export
> > devicemapper devices that are "supposed" to be visible to mount, and
> 
>  Yes, I have no clue why the dm-N crap is in /proc/partitions.
>  Probably any legacy...

I've wanted that for so long...  It's always a pain that LVM tools
work by using /dev/vgfoo/lvfoo (which is fine) but /proc/partitions
doesn't give any clue to what each dm-X device is.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  parent reply	other threads:[~2008-08-27  7:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 20:48 [PATCH] blkid: optimize dm_device_is_leaf() usage Karel Zak
2008-08-26 12:24 ` Theodore Tso
2008-08-26 13:51   ` Karel Zak
2008-08-26 14:47     ` Theodore Tso
2008-08-26 18:04       ` Theodore Tso
2008-08-26 19:44       ` Andreas Dilger
2008-08-26 20:00         ` Theodore Tso
2008-08-26 20:47       ` Karel Zak
2008-08-26 23:32         ` Theodore Tso
2008-08-27  0:19           ` Karel Zak
2008-08-27  1:21             ` Theodore Tso
2008-08-27  4:40               ` Theodore Tso
2008-08-27  8:32                 ` Karel Zak
2008-08-27  7:26             ` Andreas Dilger [this message]
2008-08-27  8:10               ` Karel Zak

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=20080827072643.GT3392@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=agk@redhat.com \
    --cc=kzak@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=sandeen@redhat.com \
    --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