From: Christoph Hellwig <hch@infradead.org>
To: Mark Haverkamp <markh@osdl.org>
Cc: 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 18:42:06 +0100 [thread overview]
Message-ID: <20050823174206.GA12359@infradead.org> (raw)
In-Reply-To: <1124815241.22518.11.camel@markh1.pdx.osdl.net>
On Tue, Aug 23, 2005 at 09:40:40AM -0700, Mark Haverkamp wrote:
>
> I'm not sure if people care about /proc/scsi, but here is a patch so you
> can cat /proc/scsi/scsi when you have a large number of scsi devices. I
> have over 4000 devices configured and when I would cat /proc/scsi/scsi I
> would see a memory allocation error. I instead used the seq_file
> iterator to display the devices. The patch is a little brute force, but
> it only took about 2.5 seconds to display 4000 devices.
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.
next prev parent reply other threads:[~2005-08-23 17:42 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 [this message]
2005-08-23 18:01 ` Patrick Mansfield
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=20050823174206.GA12359@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.