From: James Bottomley <James.Bottomley@steeleye.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kurt Garloff <garloff@suse.de>,
Linux kernel list <linux-kernel@vger.kernel.org>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] /proc/scsi/map
Date: Thu, 20 Jun 2002 12:58:34 -0400 [thread overview]
Message-ID: <200206201658.g5KGwYL04775@localhost.localdomain> (raw)
In-Reply-To: Message from Martin Dalecki <dalecki@evision-ventures.com> of "Thu, 20 Jun 2002 18:30:36 +0200." <3D12032C.7040105@evision-ventures.com>
dalecki@evision-ventures.com said:
> 1. There was the mistake of using different major numbers for SCSI and
> IDE/ATAPI devices. (disk and CD-ROM are the most striking).
Don't confuse major numbers (which are really a kernel internal thing) with
names. Major numbers serve a very useful purpose in allowing quick device
driver identification. It would be an unhappy state of affairs if we had to
parse both the major and minor numbers extensively just to identify the device
driver to handle the request. There's no reason why we can't use a consistent
naming scheme for all CD-ROMs and yet have them using different major numbers.
One of the advantages of driverfs, I think, is that it separates the device
name from a static entry in /dev which is tied to a major/minor number.
> 6. The /name is entierly redundant logically to the fact that we have
> already a unique path to the device. For "pretty" printing we have
> userspace. For PCI it's for example repeating the ID info found
> already by lspci.
The /name is useful in the enterprise for persistent device identification.
Leaves in the device tree can move as boxes are regconfigured. The name entry
helps you find your leaf again when this happens. It also helps you find the
same storage in a cluster regardless of the device driver or storage
connection method.
> And last but not least: I still don't see any kind of abstraction
> there which would allow to easly enumerate for example all disks in
> the system.
Doesn't this depend on the semantics provided in the device node (leaf)? If
you had a way of identifying disk devices (say from an empty type=disk file)
then you could do a simple find to list all the disks in the system regardless
of being SCSI, IDE, SSA etc.
James
next prev parent reply other threads:[~2002-06-20 16:58 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020620112543.GD26376@gum01m.etpnet.phys.tue.nl>
2002-06-20 15:34 ` [PATCH] /proc/scsi/map Linus Torvalds
2002-06-20 16:30 ` Martin Dalecki
2002-06-20 16:58 ` James Bottomley [this message]
2002-06-20 18:27 ` Linus Torvalds
2002-06-20 20:55 ` Martin Dalecki
2002-06-20 21:04 ` Linus Torvalds
2002-06-20 21:36 ` Martin Dalecki
2002-06-20 20:12 ` Patrick Mochel
2002-06-20 22:29 ` Martin Dalecki
2002-06-22 18:42 ` Pavel Machek
2002-06-21 21:33 ` Oliver Xymoron
2002-06-22 4:38 ` Nick Bellinger
2002-06-22 19:41 ` Douglas Gilbert
2002-06-22 19:11 ` Nick Bellinger
2002-06-25 18:13 ` Patrick Mochel
2002-06-25 16:05 ` Patrick Mochel
2002-06-25 16:57 ` Oliver Xymoron
2002-06-25 18:58 ` Patrick Mochel
2002-07-03 1:01 ` Pavel Machek
[not found] ` <20020621092943.D1243@austin.ibm.com>
2002-06-21 16:17 ` Patrick Mochel
2002-07-03 4:29 ` [PATCH] driverfs scsi for 2.5.24 Douglas Gilbert
2002-07-03 14:34 ` James Bottomley
2002-07-05 1:45 ` Douglas Gilbert
2002-07-05 18:50 ` Patrick Mochel
2002-07-05 18:31 ` Patrick Mochel
2002-06-20 18:32 ` [PATCH] /proc/scsi/map Kurt Garloff
2002-06-20 18:53 ` Linus Torvalds
2002-06-21 9:07 ` Kurt Garloff
2002-06-22 17:24 David Brownell
2002-06-22 17:48 ` Roman Zippel
2002-06-22 20:11 ` Douglas Gilbert
2002-06-22 20:57 ` Roman Zippel
2002-06-22 18:18 ` Nick Bellinger
2002-06-24 1:50 ` David Brownell
2002-06-25 16:46 ` Patrick Mochel
2002-06-25 16:33 ` Patrick Mochel
2002-06-25 17:49 ` David Brownell
2002-06-26 23:39 ` Nick Bellinger
2002-07-03 0:59 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 23:59 Grover, Andrew
[not found] <200206200711.RAA10165@thucydides.inspired.net.au>
2002-06-20 15:13 ` Linus Torvalds
2002-06-20 15:36 ` Dave Jones
2002-06-20 17:01 ` Linus Torvalds
2002-06-20 16:55 ` Andries Brouwer
[not found] ` <20020620165553.GA16897@win.tue.nl>
2002-06-20 17:52 ` Patrick Mansfield
2002-06-20 18:36 ` Linus Torvalds
2002-06-20 18:52 ` James Bottomley
2002-06-20 19:15 ` Linus Torvalds
2002-06-20 16:28 ` Benjamin Herrenschmidt
2002-06-21 0:46 ` Linus Torvalds
2002-06-20 16:49 ` Benjamin Herrenschmidt
2002-06-20 20:06 ` Oliver Xymoron
2002-06-22 18:27 ` Pavel Machek
2002-06-20 18:11 ` Linus Torvalds
2002-06-20 22:59 ` Martin Schwenke
2002-06-20 23:13 ` Linus Torvalds
2002-06-22 18:25 ` Pavel Machek
2002-06-26 16:03 ` Ihno Krumreich
2002-06-20 19:55 ` Greg KH
2002-06-20 19:18 ` Patrick Mochel
2002-06-21 6:28 ` Mike Touloumtzis
2002-06-20 0:44 Kurt Garloff
2002-06-20 5:03 ` Linus Torvalds
2002-06-20 7:09 ` Martin Schwenke
2002-06-20 11:25 ` Kurt Garloff
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=200206201658.g5KGwYL04775@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=dalecki@evision-ventures.com \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox