linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Mattias Nissler <mattias.nissler@gmx.de>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"Mikko Virkkilä" <mikko.virkkila@bluegiga.com>,
	rt2400-devel@lists.sourceforge.net,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC][PATCH] TX status reporting with help of an ack queue
Date: Tue, 16 Sep 2008 20:17:31 +0200	[thread overview]
Message-ID: <200809162017.31956.IvDoorn@gmail.com> (raw)
In-Reply-To: <1221514881.4511.118.camel@localhost>

On Monday 15 September 2008, Mattias Nissler wrote:
> On Mon, 2008-09-15 at 23:28 +0200, Ivo van Doorn wrote:
> > On Monday 15 September 2008, Johannes Berg wrote:
> > > On Mon, 2008-09-15 at 22:20 +0200, Mattias Nissler wrote:
> > > 
> > > > Well, I'm a big fan of modularizing everything in a clean way. This
> > > > whole mac80211 thingy is complex enough... But I don't really care as
> > > > long as everybody here is happy with it. Let's wait what Mikko says,
> > > > it's his code so far.
> > > 
> > > Sure. If you manage to split it out entirely, maybe by some struct that
> > > drivers embed in their private vif struct, that'd be great too.
> > 
> > I think the ACK handling could become quite complex, and although it
> > would be nice to modularize it a bit, however I am not really sure about
> > what the best approach would be for the implementation other then that
> > the driver should do as little as possible. ;)
> 
> Huh? I think a single function call for the matching in the rx path is
> enough. You call it in the rx handler for every received frame. It
> returns true if it found a match and reported the tx status (in which
> case you stop processing) or false and you can go on doing with the
> frame whatever you want. Am I missing something?

Although this isn't much overhead for a driver, but if it comes down
to a single function call anyway, why not handle it in mac80211 completely?

Ivo

  reply	other threads:[~2008-09-16 18:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1221494693.14102.22.camel@virkkmi-linux>
2008-09-15 17:11 ` [RFC][PATCH] TX status reporting with help of an ack queue Ivo van Doorn
2008-09-15 17:56   ` Mattias Nissler
2008-09-15 18:03     ` Johannes Berg
2008-09-15 19:00       ` Mattias Nissler
2008-09-15 19:21         ` Johannes Berg
2008-09-15 19:39           ` Mattias Nissler
2008-09-15 19:46             ` Johannes Berg
2008-09-15 20:20               ` Mattias Nissler
2008-09-15 20:33                 ` Johannes Berg
2008-09-15 21:01                   ` Mattias Nissler
2008-09-24  0:59                     ` John W. Linville
2008-09-24  7:40                       ` Mattias Nissler
2008-09-24  8:34                         ` Johannes Berg
2008-09-15 21:28                   ` Ivo van Doorn
2008-09-15 21:41                     ` Mattias Nissler
2008-09-16 18:17                       ` Ivo van Doorn [this message]
2008-09-17 23:08                         ` Mattias Nissler
2008-09-16  6:24                   ` Mikko Virkkilä
2008-09-16  4:58         ` Mikko Virkkilä
2008-09-16 18:18           ` Ivo van Doorn
2008-09-18 20:37             ` Mattias Nissler
2008-09-18 22:29               ` ACK matching [was: TX status reporting with help of an ack queue] Mattias Nissler
2008-09-19  9:08                 ` Mikko Virkkilä
2008-09-19  9:46                   ` Mattias Nissler
2008-09-19  9:54                     ` Johannes Berg
2008-09-19 10:19                       ` Mattias Nissler
2008-09-19 10:31                         ` Johannes Berg
2008-09-19 13:51                           ` Mattias Nissler
2008-09-19 13:55                             ` Johannes Berg
2008-09-19 14:20                             ` Mikko Virkkilä
2008-09-19 17:50                               ` Jouni Malinen
2008-09-23  6:09                                 ` Mikko Virkkilä
2008-09-23  7:05                                   ` Mattias Nissler
2008-09-19 18:30                     ` Ivo van Doorn
2008-10-19  5:49                 ` Daniel Drake

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=200809162017.31956.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mattias.nissler@gmx.de \
    --cc=mikko.virkkila@bluegiga.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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).