[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a781481a0705171204o5b25fafdm36d5970acf9119cd@mail.gmail.com>
Date: Fri, 18 May 2007 00:34:40 +0530
From: "Satyam Sharma" <satyam.sharma@...il.com>
To: "Christoph Hellwig" <hch@...radead.org>,
"Benjamin LaHaise" <bcrl@...ck.org>,
"Matthew Wilcox" <matthew@....cx>,
"Simon Arlott" <simon@...e.lp0.eu>,
"James Bottomley" <james.bottomley@...eleye.com>,
"Dave Jones" <davej@...hat.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
linux-scsi@...r.kernel.org, kernel-packagers@...r.kernel.org,
"Robert P. J. Day" <rpjday@...dspring.com>
Subject: Re: Asynchronous scsi scanning
On 5/18/07, Christoph Hellwig <hch@...radead.org> wrote:
> On Fri, May 18, 2007 at 12:17:40AM +0530, Satyam Sharma wrote:
> > However, Ben does have a point that we shouldn't force those
> > using SCSI (and wishing to use the new async scanning
> > feature) to depend on and use sysfs too
>
> yes, we do. an no, procfs is a much worse filesystem to depend
> on for drivers.
By depend on I meant being forced to build and run it. /proc is
clearly more-or-less standard that almost everybody uses, otoh
users that do not run sysfs are more common.
> if people don't want sysfs they can either do the synchronous scan
> or do their own scan in userspace.
Hmmm, actually those other users could easily write and maintain
a 20-line patch that does the wait for async scans thing for them
using /proc/scsi/scsi in any case.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists