From: 'Christoph Hellwig' <hch@infradead.org>
To: Anton Blanchard <anton@samba.org>
Cc: "Smart, James" <James.Smart@Emulex.Com>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: Emulex lpfcdriver v8.0.2 available
Date: Tue, 1 Jun 2004 20:01:18 +0100 [thread overview]
Message-ID: <20040601190118.GA22856@infradead.org> (raw)
In-Reply-To: <20040601185200.GB4239@krispykreme>
On Wed, Jun 02, 2004 at 04:52:00AM +1000, Anton Blanchard wrote:
> We gave it a spin on a ppc64 box and managed to hit the following
> backtrace when doing heavy writeout. I wonder if a number of these
> atomic allocations (in lpfc_get_scsi_buf etc) should be using a mempool,
> otherwise we could deadlock on writeout.
The ->queuecommand path has a few more problems. The number of different
memory allocation is just too many, this needs some thinking into needing
less allocations. Most allocations are happening under a spinlock and
with irqs disabled which is not exactly a good idea. And the whole
I/O submission path is very badly structured and hard to follow.
next prev parent reply other threads:[~2004-06-01 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 23:19 Emulex lpfcdriver v8.0.2 available Smart, James
2004-06-01 18:52 ` Anton Blanchard
2004-06-01 19:01 ` 'Christoph Hellwig' [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 13:03 Smart, James
2004-06-08 7:19 ` Anton Blanchard
2004-06-08 14:29 Smart, James
2004-06-09 1:39 ` Anton Blanchard
2004-06-08 14:54 Smart, James
2004-06-08 17:03 ` 'Christoph Hellwig'
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=20040601190118.GA22856@infradead.org \
--to=hch@infradead.org \
--cc=James.Smart@Emulex.Com \
--cc=anton@samba.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