From: Patrick Mansfield <patmans@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mark Haverkamp <markh@osdl.org>,
James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: /proc/scsi/scsi patch for large number of devices
Date: Tue, 23 Aug 2005 11:01:18 -0700 [thread overview]
Message-ID: <20050823180118.GB6914@us.ibm.com> (raw)
In-Reply-To: <20050823174206.GA12359@infradead.org>
On Tue, Aug 23, 2005 at 06:42:06PM +0100, Christoph Hellwig wrote:
> We had this before, and the answer is: don't use /proc/scsi if you have
> lots of device. Don't even enable the config option.
We still don't have sysfs scsi devinfo support, we need to represent it as
a modifiable list or such under sysfs.
-- Patrick Mansfield
prev parent reply other threads:[~2005-08-23 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 16:40 [PATCH] scsi: /proc/scsi/scsi patch for large number of devices Mark Haverkamp
2005-08-23 17:42 ` Christoph Hellwig
2005-08-23 18:01 ` Patrick Mansfield [this message]
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=20050823180118.GB6914@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@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