From: Jens Axboe <jens.axboe@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
device@lanana.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: regarding major number of block extended devt
Date: Thu, 4 Sep 2008 13:50:52 +0200 [thread overview]
Message-ID: <20080904115052.GF20055@kernel.dk> (raw)
In-Reply-To: <48BF2AEB.1050508@kernel.org>
On Thu, Sep 04 2008, Tejun Heo wrote:
> Hello,
>
> H. Peter Anvin wrote:
> > Thinking about it some more, one invariant this is *guaranteed* to
> > violate is:
> >
> > partition_number = partition_device - master_device
> >
> > Code that needs a partition number (which is common enough) are using
> > this invariant, because (a) it has held for 17 years and (b) because
> > there is still no alternative other that relying on fragile naming
> > scheme hacks.
> >
> > (a) we can't do anything about, but (b) we can, by introducing a
> > partition number attribute in sysfs.
>
> Yeah, that would certainly be a nice addition. Also, if partitions
> are made proper classes, they'll be easily enumerable by
> /sys/block/*/partitions/*.
>
> Jens, what do you think?
Agree, that addition definitely makes sense.
--
Jens Axboe
prev parent reply other threads:[~2008-09-04 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 12:26 regarding major number of block extended devt Tejun Heo
2008-09-02 12:35 ` Tejun Heo
2008-09-02 20:16 ` H. Peter Anvin
2008-09-03 4:13 ` Tejun Heo
2008-09-03 16:12 ` H. Peter Anvin
2008-09-03 16:21 ` Tejun Heo
2008-09-03 16:27 ` H. Peter Anvin
2008-09-03 16:45 ` Tejun Heo
2008-09-03 16:57 ` H. Peter Anvin
2008-09-03 18:11 ` H. Peter Anvin
2008-09-04 0:25 ` Tejun Heo
2008-09-04 0:28 ` H. Peter Anvin
2008-09-04 0:35 ` Tejun Heo
2008-09-04 0:43 ` H. Peter Anvin
2008-09-04 11:50 ` Jens Axboe [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=20080904115052.GF20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=device@lanana.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).