From: Jiri Pirko <jiri@resnulli.us>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Coco Li <lixiaoyan@google.com>
Subject: Re: [PATCH net] net: move dev->state into net_device_read_txrx group
Date: Mon, 18 Mar 2024 10:31:38 +0100 [thread overview]
Message-ID: <ZfgJ-txT-lTSrt6J@nanopsycho> (raw)
In-Reply-To: <20240314200845.3050179-1-edumazet@google.com>
Thu, Mar 14, 2024 at 09:08:45PM CET, edumazet@google.com wrote:
>dev->state can be read in rx and tx fast paths.
>
>netif_running() which needs dev->state is called from
>- enqueue_to_backlog() [RX path]
>- __dev_direct_xmit() [TX path]
>
>Fixes: 43a71cd66b9c ("net-device: reorganize net_device fast path variables")
>Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2024-03-18 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 20:08 [PATCH net] net: move dev->state into net_device_read_txrx group Eric Dumazet
2024-03-18 9:31 ` Jiri Pirko [this message]
2024-03-19 10:30 ` patchwork-bot+netdevbpf
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=ZfgJ-txT-lTSrt6J@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=lixiaoyan@google.com \
--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 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.