From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 0/4] ath10k: improve RX performance
Date: Tue, 24 Sep 2013 09:42:21 +0300 [thread overview]
Message-ID: <87mwn2bu0i.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1379335757-15180-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Mon, 16 Sep 2013 14:49:13 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> This patchset gives clear RX performance
> improvement on AP135. Throughput is at least
> doubled (300mbps -> 600mbps, UDP RX, 2x2).
>
> Patches depend on my RFC patch "mac80211: support
> reporting A-MSDU subframes individually".
Preferably I can apply these changes only after the mac80211 patch goes
to net-next (to avoid unnecessary rebasing). Is there a way to
workaround the need for the mac80211 patch in ath10k so that we could
apply these patches ASAP? And once the mac80211 patch is commited we
could just remove the workaround in ath10k.
--
Kalle Valo
next prev parent reply other threads:[~2013-09-24 6:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 12:49 [RFC 0/4] ath10k: improve RX performance Michal Kazior
2013-09-16 12:49 ` [RFC 1/4] ath10k: report A-MSDU subframes individually Michal Kazior
2013-09-16 12:49 ` [RFC 2/4] ath10k: document decap modes Michal Kazior
2013-09-16 12:49 ` [RFC 3/4] ath10k: cleanup RX decap handling Michal Kazior
2013-09-16 21:30 ` Kalle Valo
2013-09-17 5:19 ` Michal Kazior
2013-09-24 6:47 ` Kalle Valo
2013-09-16 12:49 ` [RFC 4/4] ath10k: align RX frames properly Michal Kazior
2013-09-24 6:42 ` Kalle Valo [this message]
2013-09-24 7:19 ` [RFC 0/4] ath10k: improve RX performance Michal Kazior
2013-09-24 7:29 ` Kalle Valo
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=87mwn2bu0i.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).