Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: Sujith <Sujith.Manoharan@atheros.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Luis Rodriguez" <Luis.Rodriguez@atheros.com>,
	"tomasw@gmail.com" <tomasw@gmail.com>
Subject: Re: [RFC] mac80211: Re-enable aggregation
Date: Mon, 20 Oct 2008 02:01:52 -0700	[thread overview]
Message-ID: <43e72e890810200201l49eea95h2f67615b536311aa@mail.gmail.com> (raw)
In-Reply-To: <1224493038.18024.36.camel@johannes.berg>

On Mon, Oct 20, 2008 at 1:57 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Mon, 2008-10-20 at 01:55 -0700, Luis R. Rodriguez wrote:
>> On Mon, Oct 20, 2008 at 1:47 AM, Sujith <Sujith.Manoharan@atheros.com> wrote:
>> > Johannes Berg wrote:
>> >  > On Mon, 2008-10-20 at 01:35 -0700, Luis R. Rodriguez wrote:
>> >  >
>> >  > > >> + *   @is_part_ampdu: set to indicate that the wireless core should should
>> >  > > >> + *           treat this frame as part of an AMPDU
>> >  > > >
>> >  > > > I thought we said we could keep the flag instead of moving to the skb
>> >  > > > here?
>> >  > >
>> >  > > That was just because the changes required to add this was too much
>> >  > > for 2.6.27 but since we don't care about this fix in 2.6.27 we can do
>> >  > > whatever is needed to fix this properly.
>> >  >
>> >  > Right, but adding random stuff into skb isn't really "properly" imho.
>> >  > And we don't really need this afaict.
>> >  >
>> >
>> > Sorry, just saw that Tomas had fixed it by setting the flag in ieee80211_tx_h_sequence().
>> > Will fix that.
>>
>> No that was a hack too, this was to minimize code changes for 2.6.27 as well.
>
> Well the fact that it's in tx_h_sequence is a bit weird, but we should
> be able to get around not using an extra bit in skb I think. Especially
> for this since it's only really between the driver and mac80211, and
> after a requeue the ampdu status might actually change.

Good point. I failed to see that. So in that case it should be as
sujith had it before my suggestion and just handle it as he had it in
the tx handlers. The problem though is that the RC algorithm should be
the one to determine if an skb is part of an ampdu for aggregation or
not IMHO. Actually this is the real question and hot topic.

When should we aggregate and should mac80211 decide that or be left to the RC.

  Luis

  reply	other threads:[~2008-10-20  9:01 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  8:22 [RFC] mac80211: Re-enable aggregation Sujith
2008-10-20  8:31 ` Johannes Berg
2008-10-20  8:35   ` Luis R. Rodriguez
2008-10-20  8:45     ` Johannes Berg
2008-10-20  8:47       ` Sujith
2008-10-20  8:55         ` Luis R. Rodriguez
2008-10-20  8:57           ` Johannes Berg
2008-10-20  9:01             ` Luis R. Rodriguez [this message]
2008-10-20  9:04               ` Johannes Berg
2008-10-20  9:05                 ` Luis R. Rodriguez
2008-10-20  9:11                 ` Sujith
2008-10-20  8:57       ` Luis R. Rodriguez
2008-10-20  8:58   ` Sujith
2008-10-20  9:12     ` Johannes Berg
2008-10-20  9:31       ` Sujith
2008-10-20  9:38         ` Johannes Berg
2008-10-20 10:35           ` Sujith
2008-10-20 12:22             ` Johannes Berg
2008-10-20 18:03               ` Sujith
2008-10-20 21:46                 ` Tomas Winkler
2008-10-21  6:46                   ` Johannes Berg
2008-10-21  7:18                   ` Sujith
2008-10-22 10:03                   ` Johannes Berg
2008-10-22 11:59                     ` Tomas Winkler
2008-10-22 17:22                       ` Johannes Berg
2008-10-23  8:57                         ` Sujith
2008-10-23 14:46                           ` Johannes Berg
2008-10-27 14:25                             ` Sujith
2008-10-27 15:04                               ` Johannes Berg
2008-10-27 15:56                                 ` Tomas Winkler
2008-10-27 16:04                                   ` Johannes Berg
2008-10-28 14:24                                     ` Tomas Winkler
2008-10-22 10:00                 ` Johannes Berg
2008-10-22 11:41                   ` Tomas Winkler
2008-10-22 17:24                     ` Johannes Berg
2008-10-23  9:31                   ` Sujith
2008-10-23 14:45                     ` Johannes Berg
2008-10-23 17:23                       ` Luis R. Rodriguez
2008-10-23 18:31                         ` Tomas Winkler
2008-10-23 20:18                           ` Luis R. Rodriguez
2008-10-23 21:17                             ` Tomas Winkler
2008-10-31  1:26                               ` Luis R. Rodriguez
2008-10-27 14:11                       ` Sujith
2008-10-27 15:07                         ` Johannes Berg
2008-10-20  9:14     ` Luis R. Rodriguez
2008-10-20  9:24       ` Johannes Berg
2008-10-20 10:07         ` Sujith
2008-10-20 10:15           ` Johannes Berg

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=43e72e890810200201l49eea95h2f67615b536311aa@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=Luis.Rodriguez@atheros.com \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomasw@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