From: "Justin T. Gibbs" <gibbs@btc.adaptec.com>
To: linux-scsi@vger.kernel.org
Subject: scsi_malloc fragmentation in 2.4.X
Date: Fri, 20 Dec 2002 13:31:58 -0700 [thread overview]
Message-ID: <70300000.1040416318@aslan.btc.adaptec.com> (raw)
Are there any plans to correct the scsi_malloc fragmentation problems
in 2.4.X? It looks like this problem has been addressed in 2.5.X by using
memory pools, but the current 2.4.X solution of just "backing off a bit"
if scsi_malloc returns NULL, is much less than ideal. At least the user
isn't assaulted by lots of "Running really short on DMA buffers" messages,
but performance does suffer when the only reason you can't queue an I/O
is that the pre-allocated S/G list memory is so poorly managed that the
available memory can't be used.
--
Justin
next reply other threads:[~2002-12-20 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 20:31 Justin T. Gibbs [this message]
2002-12-20 20:36 ` scsi_malloc fragmentation in 2.4.X Christoph Hellwig
2002-12-20 20:39 ` 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=70300000.1040416318@aslan.btc.adaptec.com \
--to=gibbs@btc.adaptec.com \
--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