From: Sam Hopkins <sah@coraid.com>
To: akpm@linux-foundation.org, hch@infradead.org
Cc: support@coraid.com, ecashin@coraid.com,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: PATCH 2.6.21-rc1 aoe: handle zero _count pages in bios
Date: Fri, 2 Mar 2007 10:51:00 -0500 [thread overview]
Message-ID: <8d855010270590ff0cad9e99e7b95863@coraid.com> (raw)
In-Reply-To: <20070301210942.ebf40993.akpm@linux-foundation.org>
> Well, given that bi_end_io() is called after the "io" has completed, I'm
> assuming that networking has completely finished with the memory by the
> time bi_end_io() gets called.
>
> I guess one can envisage situations where that might not happen, but they'd
> be terribly buggy ones, surely.
This is actually quite common when using broadcom chipsets that take a
long time to clean out the tx ring. We send a command skb out to
write some data, get the response some tens of ms later and the
command skb (with the pages) still sits in the tx ring. I've gone to
some lengths to limit the skb memory used in aoe to help with the
OOM/swap issue and this has given me headaches.
Sam
prev parent reply other threads:[~2007-03-02 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 23:15 PATCH 2.6.21-rc1 aoe: handle zero _count pages in bios Ed L. Cashin
2007-03-02 1:42 ` Andrew Morton
2007-03-02 2:29 ` Christoph Hellwig
2007-03-02 3:22 ` Andrew Morton
2007-03-02 4:30 ` Christoph Hellwig
2007-03-02 4:48 ` Andrew Morton
2007-03-02 4:49 ` Christoph Hellwig
2007-03-02 5:00 ` Andrew Morton
2007-03-02 5:03 ` Christoph Hellwig
2007-03-02 5:09 ` Andrew Morton
2007-03-02 5:15 ` Christoph Hellwig
2007-03-02 15:51 ` Sam Hopkins [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=8d855010270590ff0cad9e99e7b95863@coraid.com \
--to=sah@coraid.com \
--cc=akpm@linux-foundation.org \
--cc=ecashin@coraid.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=support@coraid.com \
/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