linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sujith <m.sujith@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Jouni.Malinen@atheros.com, Luis.Rodriguez@atheros.com,
	Senthilkumar.Balasubramanian@atheros.com
Subject: Re: [PATCH] ath9k: Use GFP_ATOMIC when allocating private area
Date: Wed, 3 Dec 2008 07:28:58 +0530	[thread overview]
Message-ID: <18741.59362.77483.600612@localhost.localdomain> (raw)
In-Reply-To: <43e72e890812021614i103235few3a19721c6ca1d0cc@mail.gmail.com>

Luis R. Rodriguez wrote:
> On Tue, Dec 2, 2008 at 5:06 AM, Sujith <Sujith.Manoharan@atheros.com> wrote:
> 
> > --- a/drivers/net/wireless/ath9k/xmit.c
> > +++ b/drivers/net/wireless/ath9k/xmit.c
> > @@ -1787,7 +1793,12 @@ int ath_tx_start(struct ath_softc *sc, struct sk_buff *skb,
> >                return -1;
> >        }
> >
> > -       ath_tx_setup_buffer(sc, bf, skb, txctl);
> > +       ret = ath_tx_setup_buffer(sc, bf, skb, txctl);
> > +       if (ret) {
> > +               DPRINTF(sc, ATH_DBG_FATAL, "TX mem alloc failure\n");
> > +               return ret;
> 
> Hm, this doesn't add the bf back to the txq, so we'd run out of bf's
> completely when on low memory, eventually leaving the list always
> empty. I'll resend with that added and a few more changes.
> 

Right.

I think the queue has to be stopped too (ieee80211_stop_queue()),
and resumed when memory is available again.

What do you think ?

Sujith

  reply	other threads:[~2008-12-03  2:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 13:06 [PATCH] ath9k: Use GFP_ATOMIC when allocating private area Sujith
2008-12-03  0:14 ` Luis R. Rodriguez
2008-12-03  1:58   ` Sujith [this message]
2008-12-03  2:09     ` Luis R. Rodriguez
2008-12-03  2:12       ` Sujith
2008-12-03  2:26         ` Luis R. Rodriguez
2008-12-03  2:41           ` Luis R. Rodriguez

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=18741.59362.77483.600612@localhost.localdomain \
    --to=m.sujith@gmail.com \
    --cc=Jouni.Malinen@atheros.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=Senthilkumar.Balasubramanian@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 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).