From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tudor Cornea <tudor.cornea@gmail.com>
Cc: <linville@tuxdriver.com>, <thomas@monjalon.net>,
<pogonarumihai@gmail.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/af_packet: fix ignoring full ring on tx
Date: Mon, 20 Sep 2021 18:44:18 +0100 [thread overview]
Message-ID: <9ec3e2cb-412a-a48b-2567-7e5ad6b1153f@intel.com> (raw)
In-Reply-To: <1631540746-38443-1-git-send-email-tudor.cornea@gmail.com>
On 9/13/2021 2:45 PM, Tudor Cornea wrote:
> The poll call can return POLLERR which is ignored, or it can return
> POLLOUT, even if there are no free frames in the mmap-ed area.
>
> We can account for both of these cases by re-checking if the next
> frame is empty before writing into it.
>
> Signed-off-by: Mihai Pogonaru <pogonarumihai@gmail.com>
> Signed-off-by: Tudor Cornea <tudor.cornea@gmail.com>
> ---
> drivers/net/af_packet/rte_eth_af_packet.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/net/af_packet/rte_eth_af_packet.c b/drivers/net/af_packet/rte_eth_af_packet.c
> index b73b211..087c196 100644
> --- a/drivers/net/af_packet/rte_eth_af_packet.c
> +++ b/drivers/net/af_packet/rte_eth_af_packet.c
> @@ -216,6 +216,25 @@ eth_af_packet_tx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
> (poll(&pfd, 1, -1) < 0))
> break;
>
> + /*
> + * Poll can return POLLERR if the interface is down
> + *
> + * It will almost always return POLLOUT, even if there
> + * are no extra buffers available
> + *
> + * This happens, because packet_poll() calls datagram_poll()
> + * which checks the space left in the socket buffer and,
> + * in the case of packet_mmap, the default socket buffer length
> + * doesn't match the requested size for the tx_ring.
> + * As such, there is almost always space left in socket buffer,
> + * which doesn't seem to be correlated to the requested size
> + * for the tx_ring in packet_mmap.
> + *
> + * This results in poll() returning POLLOUT.
> + */
> + if (ppd->tp_status != TP_STATUS_AVAILABLE)
> + break;
> +
If 'POLLOUT' doesn't indicate that there is space in the buffer, what is the
point of the 'poll()' at all?
What can we test/reproduce the mentioned behavior? Or is there a way to fix the
behavior of poll() or use an alternative of it?
OK to break on the 'POLLERR', I guess it can be detected in the 'pfd.revent'.
> /* copy the tx frame data */
> pbuf = (uint8_t *) ppd + TPACKET2_HDRLEN -
> sizeof(struct sockaddr_ll);
>
next prev parent reply other threads:[~2021-09-20 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 13:39 [dpdk-dev] [PATCH] " Tudor Cornea
2021-09-01 16:34 ` Ferruh Yigit
2021-09-06 10:23 ` Tudor Cornea
2021-09-20 17:11 ` Ferruh Yigit
2021-09-13 13:45 ` [dpdk-dev] [PATCH v2] " Tudor Cornea
2021-09-20 17:44 ` Ferruh Yigit [this message]
2021-09-29 10:03 ` Tudor Cornea
2021-10-05 15:11 ` Tudor Cornea
2021-10-26 14:30 ` Ferruh Yigit
2021-11-02 15:24 ` Tudor Cornea
2021-11-02 15:47 ` [dpdk-dev] [PATCH v3] " Tudor Cornea
2021-11-02 16:47 ` Ferruh Yigit
2021-11-03 9:31 ` [dpdk-dev] [PATCH v4] " Tudor Cornea
2021-11-04 12:07 ` Ferruh Yigit
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=9ec3e2cb-412a-a48b-2567-7e5ad6b1153f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=linville@tuxdriver.com \
--cc=pogonarumihai@gmail.com \
--cc=thomas@monjalon.net \
--cc=tudor.cornea@gmail.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).