Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "David Miller" <davem@davemloft.net>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"Guy Cohen" <guy.cohen@intel.com>,
	"Rindjunsky, Ron" <ron.rindjunsky@intel.com>
Subject: Re: Another fragmentation multiqueue kludge
Date: Thu, 24 Jul 2008 18:02:40 +0300	[thread overview]
Message-ID: <1ba2fa240807240802t2e4ae505j84fa4569b4cebd46@mail.gmail.com> (raw)
In-Reply-To: <1216911563.13587.86.camel@johannes.berg>

On Thu, Jul 24, 2008 at 5:59 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Thu, 2008-07-24 at 17:55 +0300, Tomas Winkler wrote:
>
>> > What happens if you just invert the
>> >                if (__netif_subqueue_stopped(local->mdev, i))
>> >                        continue;
>>
>> > check in ieee80211_tx_pending to read
>> >                if (!__netif_subqueue_stopped(local->mdev, i))
>> >                        continue;
>> >
>> > as I suggested yesterday?
>>
>> This is wrong since you it will actually starts queues that driver
>> didn't ask to start in the next line.
>
> Ok.
>
>> As I see it any failure in the driver's tx path will cause moving to
>> pending queue, except packets on AMPDU
>> queues that will be dropped.
>
>> That's correct for stopping because of queue overhead, not for errors.
>
> Tough luck, just drop packets on errors. If that matters to you, fix the
> driver to not run into these errors.

I don't really mind. I just want to be environment friendly and don't
want to be asked by other driver maintainers to fix their drivers :)

>> So till someone fix adm driver consider this patch It worked quite
>> well. I will also send patch that fixes the behavior in the iwlwifi
>> driver.
>
> If you fix iwlwifi we don't need this patch, and then I can instead
> remove the code from mac80211, but we can just as well merge this first
> since we'll get rid of it again.

Okay I will post both patches.
Thanks for review
Tomas

      reply	other threads:[~2008-07-24 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 21:41 Another fragmentation multiqueue kludge Tomas Winkler
2008-07-24 13:01 ` Tomas Winkler
2008-07-24 14:16   ` Johannes Berg
2008-07-24 14:37     ` Tomas Winkler
2008-07-24 14:46       ` Johannes Berg
2008-07-24 14:55         ` Tomas Winkler
2008-07-24 14:59           ` Johannes Berg
2008-07-24 15:02             ` Tomas Winkler [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=1ba2fa240807240802t2e4ae505j84fa4569b4cebd46@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=davem@davemloft.net \
    --cc=guy.cohen@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ron.rindjunsky@intel.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