Date: Wed, 5 Mar 2003 09:39:33 +0100
From: Dominik Brodowski <linux@brodo.de>
To: mochel@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: sys/fs and sys/block
Message-ID: <20030305083932.GA792@brodo.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1129
Lines: 33

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/