From: Doug Ledford <dledford@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: 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 20:00:50 -0500 [thread overview]
Message-ID: <20021218010050.GF28100@redhat.com> (raw)
In-Reply-To: <3DFFAB33.F174D272@digeo.com>
On Tue, Dec 17, 2002 at 02:54:43PM -0800, Andrew Morton wrote:
>
> wakes up.
>
> I think (hope) the plan there is to do away with the preallocated
> per-queue request lists altogether. Just allocate the requests
> direct from slab at __make_request().
So, what is the overhead of using the slab allocator on each command? If
you prealloc a reasonable queue, allocation from that queue is O(1).
Would we suffer no/little/large penalty using slab instead?
/me hasn't gone looking in the slab allocator and has no idea how well it
actually works at being a cache...
Second issue I have is that overly large request queues have never seemed
to help performance in my experience. At a certain point the overhead of
the queue and merging so many requests, etc. becomes greater than the gain
of the increased depth and starts to slow things back down. So, my
question to you, is why would we *want* to be able to have huge queues?
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-12-18 1:00 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 [this message]
2002-12-18 1:03 ` William Lee Irwin III
2002-12-18 1:22 ` Andrew Morton
2002-12-18 3:22 ` Luben Tuikov
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=20021218010050.GF28100@redhat.com \
--to=dledford@redhat.com \
--cc=akpm@digeo.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