mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Jonathan Lundell <jlundell@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adding PCI bus information to SCSI layer
Date: Tue, 1 May 2001 10:53:58 -0600	[thread overview]
Message-ID: <200105011653.f41Grwm12595@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20010501104641.C3305@nightmaster.csn.tu-chemnitz.de>
In-Reply-To: <CDF99E351003D311A8B0009027457F140810E286@ausxmrr501.us.dell.com> <200104242159.f3OLxoB07000@vindaloo.ras.ucalgary.ca> <p05100313b70bb73ce962@[207.213.214.37]> <200104270431.f3R4V4630593@vindaloo.ras.ucalgary.ca> <p05100303b70eadd613b0@[207.213.214.37]> <200105010127.f411RDP03013@vindaloo.ras.ucalgary.ca> <20010501104641.C3305@nightmaster.csn.tu-chemnitz.de>

Ingo Oeser writes:
> On Mon, Apr 30, 2001 at 07:27:13PM -0600, Richard Gooch wrote:
> > Then, vendors provide their own PCI fixups, which turn /dev/bus/pci0
> 
> What about /dev/bus/pci/0 or /dev/bus/pci/pci0 instead?
> 
> That way we could hook roots of busses (which are "." nodes, like
> if they where mounted independently) better into /dev/bus.

I'm wary of this, because Linus has stated that the current "struct
pci_dev" is really meant to be a generic thing, and it might change to
"struct dev" (now that we've renamed the old "struct dev" to "struct
netdev").

So, if the bus management code is maintaining some kind of unified
tree, it might not make sense to have a /dev/bus/pci and
/dev/bus/sbus.

> And even implement the thing as a mount point later, if we go the way
> Al Viro suggested and have independent "device filesystems"
> for the subsystems themselves.

As I understand it, Al want to turn every driver into a filesystem,
instead of using an existing FS (devfs). I can't see the point. There
certainly haven't been any technical benefits put forward for this
idea.

I spoke to Linus about this, and he wants to leave the option open for
some drivers to implement their own FS rather than calling into devfs.
He cited iSCSI as a case where this might be useful (since you need to
do something different for readdir() and lookup()). I'll be
experimenting with iSCSI myself, and I'll try out a modification to
devfs which allows a driver to register lookup() and readdir() methods
when calling devfs_mk_dir(). If this can be done sanely, then it would
provide an easier interface than using the VFS to implement a new FS.
So this particular issue remains open.

However, it's my understanding that Linus isn't trying to push
existing drivers, which work well with devfs, into implementing their
own FS. He just wants the option left open for new drivers where a
driver-specific FS makes more sense.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-05-01 16:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 21:02 Matt_Domsch
2001-04-24 21:59 ` Richard Gooch
2001-04-27  4:31   ` Richard Gooch
2001-05-01  1:27     ` Richard Gooch
2001-05-01  8:46       ` Ingo Oeser
2001-05-01 16:53       ` Richard Gooch [this message]
2001-05-01 20:32         ` Alan Cox
2001-05-02 15:03           ` Ingo Oeser
2001-05-02 15:54             ` Alan Cox
2001-05-03  8:57           ` Chris Wedgwood
2001-05-03  9:49             ` Alan Cox
2001-05-03 10:23               ` Chris Wedgwood
2001-04-24 23:16 ` Jonathan Lundell
2001-04-27  5:24   ` Jonathan Lundell
2001-05-01 14:38     ` Jonathan Lundell
2001-05-03  7:32     ` Kai Henningsen
2001-05-03  7:51     ` Jonathan Lundell
2001-05-11 16:32       ` Ralf Baechle
2001-05-11 23:00         ` Steven Willoughby
2001-05-11 22:49       ` Jonathan Lundell
2001-05-12  2:20         ` Ralf Baechle
2001-05-12  4:21         ` Jonathan Lundell
     [not found] <p0510030db7221c090810@[10.128.7.49]=FE2>
2001-05-12 11:00 ` Kai Henningsen

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=200105011653.f41Grwm12595@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=jlundell@pobox.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®