All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v2] mac80211: temporarily disable reorder release timer
Date: Fri, 8 Oct 2010 22:49:20 +0200	[thread overview]
Message-ID: <201010082249.20545.chunkeey@googlemail.com> (raw)
In-Reply-To: <AANLkTi=LxUqST506VGiM8RpEZXrJ6_EWVRiJHboGVv5i@mail.gmail.com>

On Friday 08 October 2010 22:40:39 Luis R. Rodriguez wrote:
> On Fri, Oct 8, 2010 at 1:35 PM, Christian Lamparter
> <chunkeey@googlemail.com> wrote:
> > Several serve threading problems in the current
> > release reorder timer implementation have been
> > discovered.
> >
> > A lengthy discussion - which lists some of the
> > pitfalls and possible solutions - can be found at:
> >  http://marc.info/?t=128635927000001
> >
> > But due to the complicated nature of the subject and
> > the imminent advent of a new -rc cycle, it was
> > decided to disable the feature for the time being.
> >
> > Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> 
> This patch lacks documentation of the impact of this patch, while it
> may fix a lock issue, the does not address what happens when the patch
> is actually applied.
? It just disables the timer. The actual reorder code
is left untouched, everything is the same as in Linus'
2.6.36-rcX tree.

Or what impact are you talking about?

  reply	other threads:[~2010-10-08 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 20:35 [PATCH v2] mac80211: temporarily disable reorder release timer Christian Lamparter
2010-10-08 20:40 ` Luis R. Rodriguez
2010-10-08 20:49   ` Christian Lamparter [this message]
2010-10-08 21:22     ` Luis R. Rodriguez
2010-10-08 21:57       ` Christian Lamparter

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=201010082249.20545.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --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 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.