From: Jens Axboe <axboe@suse.de>
To: Ed L Cashin <ecashin@coraid.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ATA over Ethernet driver for 2.6.9 (with changes)
Date: Mon, 13 Dec 2004 21:19:41 +0100 [thread overview]
Message-ID: <20041213201941.GC3399@suse.de> (raw)
In-Reply-To: <87k6rmuqu4.fsf@coraid.com>
On Mon, Dec 13 2004, Ed L Cashin wrote:
> * use mempool allocation in make_request_fn
It's not good enough, if cannot use a higher allocation priority that
GFP_NOIO here - basically guarantee that your allocation will not block
on further io. Currently you have the very same deadlock as before, the
mempool does not help you since you call into the allocator and deadlock
before ever blocking on the mempool.
--
Jens Axboe
next prev parent reply other threads:[~2004-12-13 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 16:04 [PATCH] ATA over Ethernet driver for 2.6.9 (with changes) Ed L Cashin
2004-12-13 20:19 ` Jens Axboe [this message]
2004-12-14 13:39 ` Ed L Cashin
2004-12-14 13:52 ` Jens Axboe
2004-12-13 21:23 ` Jan-Benedict Glaw
2004-12-14 20:39 ` Ed L Cashin
2004-12-13 21:54 ` Greg KH
2004-12-14 13:50 ` Ed L Cashin
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=20041213201941.GC3399@suse.de \
--to=axboe@suse.de \
--cc=ecashin@coraid.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).