From: Luben Tuikov <luben@splentec.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Doug Ledford <dledford@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
"Justin T. Gibbs" <gibbs@scsiguy.com>,
linux-scsi@vger.kernel.org
Subject: Re: slave_destroy called in scsi_scan.c:scsi_probe_and_add_lun()
Date: Tue, 17 Dec 2002 22:22:44 -0500 [thread overview]
Message-ID: <3DFFEA04.2000803@splentec.com> (raw)
In-Reply-To: <3DFFCDC0.C456BBDB@digeo.com>
Andrew Morton wrote:
>
[...]
> So I expect that in practice we would be unlikely to go beyond
> 128 requests per direction per queue. But it should be an
> option, and it should work well.
I have an actual number: 512*. This is the number which /proc/slabinfo
tells me, and I suspect that the number of active (LLDD owner) commands
is a lot less than this.**
* I get this number when writing (I->T) just over 100 GiB file,
using a ``mini'' scsi-core which I wrote for a project at work.
And this, 512, number is the largest value I've seen so far,
i.e. the largest pool.
** I can actually obtain the exact (average) number of active commands
but I don't think that there's any need to. (QED)
But, yes, using the slab allocator (with the appropriate flags(!), etc...)
isn't a bad idea at all.
--
Luben
next prev parent reply other threads:[~2002-12-18 3:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 23:19 slave_destroy called in scsi_scan.c:scsi_probe_and_add_lun() Justin T. Gibbs
2002-12-17 0:03 ` Douglas Gilbert
2002-12-17 5:41 ` Doug Ledford
2002-12-17 20:25 ` Justin T. Gibbs
2002-12-17 22:24 ` Doug Ledford
2002-12-17 22:33 ` Christoph Hellwig
2002-12-17 22:54 ` Andrew Morton
2002-12-18 1:00 ` Doug Ledford
2002-12-18 1:03 ` William Lee Irwin III
2002-12-18 1:22 ` Andrew Morton
2002-12-18 3:22 ` Luben Tuikov [this message]
2002-12-18 2:07 ` Justin T. Gibbs
2002-12-18 3:35 ` Doug Ledford
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=3DFFEA04.2000803@splentec.com \
--to=luben@splentec.com \
--cc=akpm@digeo.com \
--cc=dledford@redhat.com \
--cc=gibbs@scsiguy.com \
--cc=hch@infradead.org \
--cc=linux-scsi@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