From: Dominik Brodowski <linux@brodo.de>
To: mochel@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: sys/fs and sys/block
Date: Wed, 5 Mar 2003 09:39:33 +0100 [thread overview]
Message-ID: <20030305083932.GA792@brodo.de> (raw)
Hi Pat,
I'm a bit surprised to find yet another top-level directory in sysfs --
"fs". Wouldn't it be a bit more driver-model-conforming if there'd be a
"bus_type block_bus_type" with devices like "hda", "fd0", "loop0", and each
such block device registers a device like "hda1" for partitions of "bus_type
filesystem_bus_type" (or "partition_bus_type"). And the device drivers for
these devices are then the filesystems.
A few example on how this could look like in sysfs:
sys/devices/pci0/00:07.1/ide0/hda/hda1
sys/devices/platform/fd0/fd0
? sys/devices/virtual/loop0 (a new "virtual" bus would allow us to register
"virtual" and "dummy" devices)
sys/bus/filesystem/devices/hda1
sys/bus/filesystem/devices/fd0
sys/bus/filesystem/drivers/xfs
sys/bus/block/devices/hda
Oh, and is the kobj in super_block (which was added in the same sys/fs
patch) used anywhere?
Dominik
next reply other threads:[~2003-03-05 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 8:39 Dominik Brodowski [this message]
2003-03-05 17:05 ` sys/fs and sys/block Patrick Mochel
2003-03-07 12:02 ` Nikita Danilov
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=20030305083932.GA792@brodo.de \
--to=linux@brodo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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