ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 0/5] ath10k: tx performance patches
Date: Fri, 20 Sep 2013 08:18:40 +0300	[thread overview]
Message-ID: <87vc1wgjf3.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <1379508202-9660-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 18 Sep 2013 14:43:17 +0200")

Michal Kazior <michal.kazior@tieto.com> writes:

> Hi,
>
> This patchset reduces CPU load and improves
> improves TX performance on AP135 by additional
> 30mbps (give or take; 560mbps -> 590mbps), at
> least on my testbed.
>
>
> Michal Kazior (5):
>   ath10k: use num_pending_tx instead of msdu id bitmap
>   ath10k: avoid needless memset on TX path
>   ath10k: decouple HTT TX completions
>   ath10k: cleanup HTT TX functions
>   ath10k: use msdu headroom to store txfrag

Thanks, all five applied.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      parent reply	other threads:[~2013-09-20  5:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 12:43 [PATCH 0/5] ath10k: tx performance patches Michal Kazior
2013-09-18 12:43 ` [PATCH 1/5] ath10k: use num_pending_tx instead of msdu id bitmap Michal Kazior
2013-09-18 12:43 ` [PATCH 2/5] ath10k: avoid needless memset on TX path Michal Kazior
2013-09-18 12:43 ` [PATCH 3/5] ath10k: decouple HTT TX completions Michal Kazior
2013-09-18 12:43 ` [PATCH 4/5] ath10k: cleanup HTT TX functions Michal Kazior
2013-09-18 12:43 ` [PATCH 5/5] ath10k: use msdu headroom to store txfrag Michal Kazior
2013-09-20  5:18 ` Kalle Valo [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=87vc1wgjf3.fsf@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