All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "michal.kazior@tieto.com" <michal.kazior@tieto.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: disable wake_tx_queue for older devices
Date: Thu, 7 Jul 2016 16:30:48 +0000	[thread overview]
Message-ID: <87zipt1kco.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1467201146-6844-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 29 Jun 2016 13:52:26 +0200")

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

> Ideally wake_tx_queue should be used regardless as
> it is a requirement for reducing bufferbloat and
> implementing airtime fairness in the future.
>
> However some setups (typically low-end platforms
> hosting QCA988X) suffer performance regressions
> with the current wake_tx_queue implementation.
> Therefore disable it unless it is really
> beneficial with current codebase (which is when
> firmware supports smart pull-push tx scheduling).
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>

I think it's too late to send this to 4.7 anymore (and this due to my
vacation). So I'm planning to queue this to 4.8, but if the feedback is
positive we can always send this to a 4.7 stable release.

-- 
Kalle Valo

WARNING: multiple messages have this Message-ID (diff)
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "michal.kazior@tieto.com" <michal.kazior@tieto.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: disable wake_tx_queue for older devices
Date: Thu, 7 Jul 2016 16:30:48 +0000	[thread overview]
Message-ID: <87zipt1kco.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1467201146-6844-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 29 Jun 2016 13:52:26 +0200")

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

> Ideally wake_tx_queue should be used regardless as
> it is a requirement for reducing bufferbloat and
> implementing airtime fairness in the future.
>
> However some setups (typically low-end platforms
> hosting QCA988X) suffer performance regressions
> with the current wake_tx_queue implementation.
> Therefore disable it unless it is really
> beneficial with current codebase (which is when
> firmware supports smart pull-push tx scheduling).
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>

I think it's too late to send this to 4.7 anymore (and this due to my
vacation). So I'm planning to queue this to 4.8, but if the feedback is
positive we can always send this to a 4.7 stable release.

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

  reply	other threads:[~2016-07-07 16:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 12:47 [RFC/RFT] ath10k: disable wake_tx_queue for older devices Michal Kazior
2016-05-17 12:47 ` Michal Kazior
2016-06-02 13:14 ` Valo, Kalle
2016-06-02 13:14   ` Valo, Kalle
2016-06-08 11:39   ` Roman Yeryomin
2016-06-08 11:39     ` Roman Yeryomin
2016-06-29  8:58     ` Valo, Kalle
2016-06-29  8:58       ` Valo, Kalle
2016-06-29 11:52 ` [PATCH] " Michal Kazior
2016-06-29 11:52   ` Michal Kazior
2016-07-07 16:30   ` Valo, Kalle [this message]
2016-07-07 16:30     ` Valo, Kalle
2016-07-31 23:35     ` Roman Yeryomin
2016-07-31 23:35       ` Roman Yeryomin
2016-08-01  9:04       ` Dave Taht
2016-08-01  9:04         ` Dave Taht
2016-08-04 10:07         ` Roman Yeryomin
2016-08-04 10:07           ` Roman Yeryomin
2016-08-04 12:02           ` Dave Taht
2016-08-04 12:02             ` Dave Taht
2016-07-19 13:19   ` Kalle Valo
2016-07-19 13:19     ` 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=87zipt1kco.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 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.