From: Leon Romanovsky <leon@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: add macro netif_subqueue_completed_wake
Date: Thu, 13 Apr 2023 16:05:48 +0300 [thread overview]
Message-ID: <20230413130548.GP17993@unreal> (raw)
In-Reply-To: <61877868-4fb7-4b9a-fd0d-41da1d9149b4@gmail.com>
On Wed, Apr 12, 2023 at 11:25:10PM +0200, Heiner Kallweit wrote:
> Add netif_subqueue_completed_wake, complementing the subqueue versions
> netif_subqueue_try_stop and netif_subqueue_maybe_stop.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> include/net/netdev_queues.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Please send together with in-tree user of this macro.
Thanks
>
> diff --git a/include/net/netdev_queues.h b/include/net/netdev_queues.h
> index b26fdb441..d68b0a483 100644
> --- a/include/net/netdev_queues.h
> +++ b/include/net/netdev_queues.h
> @@ -160,4 +160,14 @@ netdev_txq_completed_mb(struct netdev_queue *dev_queue,
> netif_txq_maybe_stop(txq, get_desc, stop_thrs, start_thrs); \
> })
>
> +#define netif_subqueue_completed_wake(dev, idx, pkts, bytes, \
> + get_desc, start_thrs) \
> + ({ \
> + struct netdev_queue *txq; \
> + \
> + txq = netdev_get_tx_queue(dev, idx); \
> + netif_txq_completed_wake(txq, pkts, bytes, \
> + get_desc, start_thrs); \
> + })
> +
> #endif
> --
> 2.40.0
>
prev parent reply other threads:[~2023-04-13 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 21:25 [PATCH net-next] net: add macro netif_subqueue_completed_wake Heiner Kallweit
2023-04-13 13:05 ` Leon Romanovsky [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=20230413130548.GP17993@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).