public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: 'David Brownell' <david-b@pacbell.net>,
	'Nick Bellinger' <nickb@attheoffice.org>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Patrick Mochel <mochel@osdl.org>
Subject: Re: driverfs is not for everything! (was: [PATCH] /proc/scsi/map )
Date: Mon, 24 Jun 2002 14:09:13 -0400	[thread overview]
Message-ID: <200206241809.g5OI9Ds02886@localhost.localdomain> (raw)
In-Reply-To: Message from "Grover, Andrew" <andrew.grover@intel.com> of "Mon, 24 Jun 2002 10:35:53 PDT." <59885C5E3098D511AD690002A5072D3C02AB7F53@orsmsx111.jf.intel.com>

andrew.grover@intel.com said:
> If a device can be accessed by multiple machines concurrently, it
> should not be in driverfs. 

On that argument, we'll eliminate almost all Fibre Channel devices!

I think the qualification for appearing in driverfs is actually possessing a 
driver.  Therefore, we accept FC and iSCSI.  Things which appear as 
FileSystems are debatable, but not anything which has a real device driver.

> We need a device tree to do PM. If driverfs's PM capabilities are hurt
> because it doesn't stay true to that, then the featureitis has gone
> too far. 

Perhaps it's more a question of whether power management belongs as an every 
unit item in driverfs.  As you say, we get problems where the device is shared 
between multiple computers.

James



  parent reply	other threads:[~2002-06-24 18:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <andrew.grover@intel.com>
2002-06-24 17:35 ` driverfs is not for everything! (was: [PATCH] /proc/scsi/map ) Grover, Andrew
2002-06-24 18:04   ` David Brownell
2002-06-24 18:09   ` James Bottomley [this message]
2002-06-24 19:23     ` Oliver Xymoron
2002-06-25 18:38     ` Patrick Mochel
2002-06-24 18:32   ` Roman Zippel
2002-06-24 22:47   ` John Summerfield
2002-06-25 18:35   ` Patrick Mochel
2002-07-01  2:41   ` Pavel Machek
2002-06-24 18:47 Grover, Andrew
2002-06-24 19:03 ` Oliver Xymoron
  -- strict thread matches above, loose matches on Subject: below --
2002-06-24 18:37 Grover, Andrew
2002-06-23 22:59 driverfs is not for everything! (was: [PATCH] /proc/scsi/map) Grover, Andrew
2002-06-24  1:34 ` David Brownell
2002-06-24  5:18 ` Nick Bellinger
2002-06-24  6:41   ` Brad Hards
2002-06-25 18:18 ` Patrick Mochel

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=200206241809.g5OI9Ds02886@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=andrew.grover@intel.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=nickb@attheoffice.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