All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Abhishek Kumar <kuabhs@chromium.org>
Cc: briannorris@chromium.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org, dianders@chromium.org,
	pillair@codeaurora.org, "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	ath10k@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ath10k: enable threaded napi on ath10k driver
Date: Wed, 22 Dec 2021 08:43:04 +0200	[thread overview]
Message-ID: <87k0fx2l8n.fsf@kernel.org> (raw)
In-Reply-To: <CACTWRwtn+xwVfdFC_1ZAEGC41+gqjDNpTk46vctejnF74Pf+AQ@mail.gmail.com> (Abhishek Kumar's message of "Tue, 14 Dec 2021 14:48:13 -0800")

Abhishek Kumar <kuabhs@chromium.org> writes:

> This patch is to trigger a discussion on the best approach to enable
> threaded NAPI on ath10k. Threaded NAPI feature was added in (net:
> extract napi poll functionality to __napi_poll() commit
> 898f8015ffe74118e7b461827451f2cc6e51035b) and showed good results on
> ath10k snoc based solution.
>
> If we come to a consensus with this as the best approach to enable
> threaded NAPI on ath10k, then we can moved ahead with the
> implementation and enable across sdio and pci, or if there is any
> objection then we can discuss it here.

Few tips:

It's a good idea to mark patches like this with "[PATCH RFC]":

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#use_rfc_or_rft_for_patches_not_ready

And you can add a text like the above after the "---" line in the patch
itself.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

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

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Abhishek Kumar <kuabhs@chromium.org>
Cc: briannorris@chromium.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org, dianders@chromium.org,
	pillair@codeaurora.org, "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	ath10k@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ath10k: enable threaded napi on ath10k driver
Date: Wed, 22 Dec 2021 08:43:04 +0200	[thread overview]
Message-ID: <87k0fx2l8n.fsf@kernel.org> (raw)
In-Reply-To: <CACTWRwtn+xwVfdFC_1ZAEGC41+gqjDNpTk46vctejnF74Pf+AQ@mail.gmail.com> (Abhishek Kumar's message of "Tue, 14 Dec 2021 14:48:13 -0800")

Abhishek Kumar <kuabhs@chromium.org> writes:

> This patch is to trigger a discussion on the best approach to enable
> threaded NAPI on ath10k. Threaded NAPI feature was added in (net:
> extract napi poll functionality to __napi_poll() commit
> 898f8015ffe74118e7b461827451f2cc6e51035b) and showed good results on
> ath10k snoc based solution.
>
> If we come to a consensus with this as the best approach to enable
> threaded NAPI on ath10k, then we can moved ahead with the
> implementation and enable across sdio and pci, or if there is any
> objection then we can discuss it here.

Few tips:

It's a good idea to mark patches like this with "[PATCH RFC]":

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#use_rfc_or_rft_for_patches_not_ready

And you can add a text like the above after the "---" line in the patch
itself.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2021-12-22  6:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 22:39 [PATCH] ath10k: enable threaded napi on ath10k driver Abhishek Kumar
2021-12-14 22:39 ` Abhishek Kumar
2021-12-14 22:48 ` Abhishek Kumar
2021-12-14 22:48   ` Abhishek Kumar
2021-12-22  6:43   ` Kalle Valo [this message]
2021-12-22  6:43     ` Kalle Valo
2021-12-15  2:28 ` Jakub Kicinski
2021-12-15  2:28   ` Jakub Kicinski
2021-12-22  6:44 ` Kalle Valo
2021-12-22  6:44   ` Kalle Valo
2021-12-22 11:16 ` Felix Fietkau
2021-12-22 11:16   ` Felix Fietkau
2021-12-23 15:49   ` Dave Taht
2021-12-23 15:49     ` Dave Taht

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=87k0fx2l8n.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=briannorris@chromium.org \
    --cc=davem@davemloft.net \
    --cc=dianders@chromium.org \
    --cc=kuabhs@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pillair@codeaurora.org \
    /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.