From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Ron Rindjunksi <ron.rindjunski@intel.com>
Subject: [PATCH 0/2] mac80211: use multiqueue netdev
Date: Sat, 17 May 2008 00:57:12 +0200 [thread overview]
Message-ID: <20080516225712.794319000@sipsolutions.net> (raw)
This patch (well, there are two, but the first one is just some
sanity checking) converts mac80211 to use a multiqueue netdev.
The next step will be to re-do fragmentation taking into account
proper A-MPDU handling etc. but I would love to have Ron look over
that too since he's much more familiar with the A-MPDU stuff.
johannes
next reply other threads:[~2008-05-16 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 22:57 Johannes Berg [this message]
2008-05-16 22:57 ` [PATCH 1/2] mac80211: dont allow fragmentation and requeuing on A-MPDU queues Johannes Berg
2008-05-16 22:57 ` [PATCH 2/2] mac80211: use multi-queue master netdevice Johannes Berg
2008-05-17 9:05 ` Waskiewicz Jr, Peter P
2008-05-16 23:07 ` [PATCH 0/2] mac80211: use multiqueue netdev Johannes Berg
2008-05-19 16:12 ` Ron Rindjunsky
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=20080516225712.794319000@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=ron.rindjunski@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;
as well as URLs for NNTP newsgroup(s).