From: "H. Peter Anvin" <hpa@zytor.com>
To: Tejun Heo <tj@kernel.org>
Cc: device@lanana.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: regarding major number of block extended devt
Date: Wed, 03 Sep 2008 17:43:44 -0700 [thread overview]
Message-ID: <48BF2F40.5050906@zytor.com> (raw)
In-Reply-To: <48BF2D4E.4090906@kernel.org>
Tejun Heo wrote:
> H. Peter Anvin wrote:
>> Note that addition /partitions/ is somewhat unlikely to be useful, since
>> existing code will have to search through random crap in sysfs to look
>> for the partition directories anyway.
>
> Currently it has to list /sys/block/DEV/DEV[-]N/. With proper
> classification, it can do /sys/block/*/partitions/*. We'll need to keep
> around symlinks at the root level. It also plays well with how other
> subsystems have been changing.
>
Yes, my point was mostly that in order to support older kernels, most
code is going to want to just access /sys/block/DEV/DEV*N/ anyway. What
I have done in my code is I do a readdir() on /sys/block/DEV and look
for subdirectories with a "dev" member.
Changing them to symlinks would actually break at least my code
(arguably bad programming on my part), since optimize by looking for
DT_DIR.
-hpa
next prev parent reply other threads:[~2008-09-04 0:45 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 [this message]
2008-09-04 11:50 ` Jens Axboe
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=48BF2F40.5050906@zytor.com \
--to=hpa@zytor.com \
--cc=device@lanana.org \
--cc=jens.axboe@oracle.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 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.