From: Doug Ledford <dledford@redhat.com>
To: "Justin T. Gibbs" <gibbs@btc.adaptec.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi_malloc fragmentation in 2.4.X
Date: Fri, 20 Dec 2002 15:39:02 -0500 [thread overview]
Message-ID: <20021220203902.GF4166@redhat.com> (raw)
In-Reply-To: <70300000.1040416318@aslan.btc.adaptec.com>
On Fri, Dec 20, 2002 at 01:31:58PM -0700, Justin T. Gibbs wrote:
> 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"
Not in my plans anyway. There's so much broken in 2.4 that fixing it
means upgrading to 2.6 when available IMHO, so that's why I'm trying to
get 2.6 fixed up as fast as possible and letting 2.4 be as it is.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
prev parent reply other threads:[~2002-12-20 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 20:31 scsi_malloc fragmentation in 2.4.X Justin T. Gibbs
2002-12-20 20:36 ` Christoph Hellwig
2002-12-20 20:39 ` Doug Ledford [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=20021220203902.GF4166@redhat.com \
--to=dledford@redhat.com \
--cc=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