From: Wang Liang <wangliang74@huawei.com>
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: <bjorn@kernel.org>, <magnus.karlsson@intel.com>,
<maciej.fijalkowski@intel.com>, <jonathan.lemon@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <horms@kernel.org>, <ast@kernel.org>,
<daniel@iogearbox.net>, <hawk@kernel.org>,
<john.fastabend@gmail.com>, <yuehaibing@huawei.com>,
<zhangchangzhong@huawei.com>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] xsk: correct tx_ring_empty_descs count statistics
Date: Tue, 1 Apr 2025 10:35:45 +0800 [thread overview]
Message-ID: <0d1b689c-c0ef-460a-9969-ff5aebbb8fac@huawei.com> (raw)
In-Reply-To: <Z-sRF0G43HpGiGwH@mini-arch>
在 2025/4/1 6:03, Stanislav Fomichev 写道:
> On 03/31, Stanislav Fomichev wrote:
>> On 03/29, Wang Liang wrote:
>>> The tx_ring_empty_descs count may be incorrect, when set the XDP_TX_RING
>>> option but do not reserve tx ring. Because xsk_poll() try to wakeup the
>>> driver by calling xsk_generic_xmit() for non-zero-copy mode. So the
>>> tx_ring_empty_descs count increases once the xsk_poll()is called:
>>>
>>> xsk_poll
>>> xsk_generic_xmit
>>> __xsk_generic_xmit
>>> xskq_cons_peek_desc
>>> xskq_cons_read_desc
>>> q->queue_empty_descs++;
>>>
>>> To avoid this count error, add check for tx descs before send msg in poll.
>>>
>>> Fixes: df551058f7a3 ("xsk: Fix crash in poll when device does not support ndo_xsk_wakeup")
>>> Signed-off-by: Wang Liang <wangliang74@huawei.com>
>> Acked-by: Stanislav Fomichev <sdf@fomichev.me>
> Hmm, wait, I stumbled upon xskq_has_descs again and it looks only at
> cached prod/cons. How is it supposed to work when the actual tx
> descriptor is posted? Is there anything besides xskq_cons_peek_desc from
> __xsk_generic_xmit that refreshes cached_prod?
Yes, you are right!
How about using xskq_cons_nb_entries() to check free descriptors?
Like this:
diff --git a/net/xdp/xsk.c b/net/xdp/xsk.c
index e5d104ce7b82..babb7928d335 100644
--- a/net/xdp/xsk.c
+++ b/net/xdp/xsk.c
@@ -993,7 +993,7 @@ static __poll_t xsk_poll(struct file *file, struct
socket *sock,
if (pool->cached_need_wakeup) {
if (xs->zc)
xsk_wakeup(xs, pool->cached_need_wakeup);
- else if (xs->tx)
+ else if (xs->tx && xskq_cons_nb_entries(xs->tx, 1))
/* Poll needs to drive Tx also in copy mode */
xsk_generic_xmit(sk);
}
next prev parent reply other threads:[~2025-04-01 2:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 6:15 Wang Liang
2025-03-31 15:22 ` Stanislav Fomichev
2025-03-31 22:03 ` Stanislav Fomichev
2025-04-01 2:35 ` Wang Liang [this message]
2025-04-01 6:57 ` Magnus Karlsson
2025-04-01 7:39 ` Wang Liang
2025-04-01 7:43 ` Wang Liang
2025-04-01 8:12 ` Magnus Karlsson
2025-04-01 9:33 ` Wang Liang
2025-04-01 11:00 ` Magnus Karlsson
2025-04-02 2:38 ` Wang Liang
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=0d1b689c-c0ef-460a-9969-ff5aebbb8fac@huawei.com \
--to=wangliang74@huawei.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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
all inboxes | Powered by JetHome®