From: Michael Buesch <mb@bu3sch.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: What should wireless drivers do under -ENOMEM
Date: Fri, 21 Nov 2008 20:01:46 +0100 [thread overview]
Message-ID: <200811212001.46336.mb@bu3sch.de> (raw)
In-Reply-To: <43e72e890811211055x19882fa1l5ced86b6a031a203@mail.gmail.com>
On Friday 21 November 2008 19:55:12 Luis R. Rodriguez wrote:
> Under heavy stress you can sometimes run into -ENOMEM and you inform
> the callers. Now ath5k/ath9k both require dev_alloc_skb()'ing some
> buffers when RXing. Right now we simply move on, but I think it'd be
> nicer to inform mac80211 and let mac80211 decide. If the system is
Well, what should mac80211 decide?
If you are under such heavy load that memory allocations fail, we really have
only one chance. That is drop the network traffic until memory allocation
works again.
I don't see anything else we can do.
--
Greetings Michael.
prev parent reply other threads:[~2008-11-21 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 18:55 What should wireless drivers do under -ENOMEM Luis R. Rodriguez
2008-11-21 19:01 ` Michael Buesch [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=200811212001.46336.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.