linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v4] mac80211: re-enable aggregation on 2.6.27
Date: Thu, 2 Oct 2008 05:49:41 -0700	[thread overview]
Message-ID: <20081002124941.GB5960@tesla> (raw)
In-Reply-To: <1ba2fa240810020427m307404b6x434830e2a3e5bf1b@mail.gmail.com>

On Thu, Oct 02, 2008 at 04:27:36AM -0700, Tomas Winkler wrote:
> On Wed, Oct 1, 2008 at 10:16 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > On Tue, Sep 30, 2008 at 5:07 PM, Tomas Winkler <tomasw@gmail.com> wrote:
> >> On Tue, Sep 30, 2008 at 6:25 PM, Luis R. Rodriguez
> >> <lrodriguez@atheros.com> wrote:
> >>> A quick test indicates it works but the removal is still an issue.
> >>
> >> I didn't implement it yet I just wanted a feedback if I'm in correct
> >> direction with the starting part.
> >
> > Seems reasonable so far, my concern so far was just the introduction
> > of a new spinlock for the ba_session list, but I can't see yet a
> > better way.
> >
> > At this point I've given up hope of this getting merged but I do think
> > distributions using 2.6.27 will want this anyway so we might as well
> > finish the job and maintain it ourselves should it not get merged.
> > What do you think?
> >
> >> yes ieee80211_init_agg()
> >
> > Thanks, I'm using this now.
> >
> >>> I don't think it was locking before under the code which is now
> >>> under initiate_aggr_and_timer() though.
> >>
> >> Correct you cannot lock this part it leads to soft lock.
> >
> > Oh ok v3 had this order.
> >
> >  Luis
> >
> I'm proposing to drop this implementation at all and focus on correct
> solution , this is just too messy.
> Maybe develop it over 2.6.27 so it will be maybe merge to stable
> release as well.

Well a clean solution would you to either move aggregation
queues to your drivers completely or make it optional (not sure if this
is worth it, what other hardware requires this???), which is a huge
change, which would not go into 2.6.27 for sure and I feel perhaps
distributions would be more reluctant to carry around.

Either way we still need an aggregation fix 2.6.27.

  Luis

      reply	other threads:[~2008-10-02 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 16:02 [RFC v4] mac80211: re-enable aggregation on 2.6.27 Luis R. Rodriguez
2008-09-30 16:23 ` Luis R. Rodriguez
2008-09-30 20:18 ` Tomas Winkler
2008-09-30 15:25   ` Luis R. Rodriguez
2008-10-01  0:07     ` Tomas Winkler
2008-10-01 11:54       ` Luis R. Rodriguez
2008-10-01 19:16       ` Luis R. Rodriguez
2008-10-02 11:27         ` Tomas Winkler
2008-10-02 12:49           ` Luis R. Rodriguez [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=20081002124941.GB5960@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@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;
as well as URLs for NNTP newsgroup(s).