DPDK patches and discussions
 help / color / mirror / Atom feed
From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: dev@dpdk.org
Subject: [PATCH 00/10] port: implement output port non-blocking behavior
Date: Fri,  5 Aug 2022 22:00:19 +0000	[thread overview]
Message-ID: <20220805220029.1096212-1-cristian.dumitrescu@intel.com> (raw)

In case of blocking behavior, the output port retries sending the
packets that could not be sent successfully. The retry can take place
potentially forever in case the Ethernet device or the ring consumer
are down, which leads to deadlock.

In case of the non-blocking behavior introduced by this series, the
packets that could not be sent successfully are dropped and the
associated drop statistics counters are incremented.

Depends-on: series-24205 ("net/softnic: replace the legacy pipeline with SWX pipeline")

Cristian Dumitrescu (10):
  port: add output port packet drop statistics couters
  port: adjust the sink port counters
  port: rework the Ethernet device output port behavior to non-blocking
  port: free buffered packets on Ethernet device output port free
  port: prevent unnecessary flush for the Ethernet device output port
  port: rework the ring output port behavior to non-blocking
  port: free buffered packets on ring output port free
  port: prevent unnecessary flush for the ring output port
  examples/pipeline: print the output port packet drop counters
  net/softnic: print the output port packet drop counters

 drivers/net/softnic/rte_eth_softnic_cli.c |   4 +
 examples/pipeline/cli.c                   |   4 +
 lib/port/rte_swx_port.h                   |  10 +-
 lib/port/rte_swx_port_ethdev.c            | 117 +++++++++++++++-------
 lib/port/rte_swx_port_ring.c              | 113 ++++++++++++++-------
 lib/port/rte_swx_port_source_sink.c       |   8 +-
 6 files changed, 177 insertions(+), 79 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-08-05 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 22:00 Cristian Dumitrescu [this message]
2022-08-05 22:00 ` [PATCH 01/10] port: add output port packet drop statistics couters Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 02/10] port: adjust the sink port counters Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 03/10] port: rework the Ethernet device output port behavior to non-blocking Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 04/10] port: free buffered packets on Ethernet device output port free Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 05/10] port: prevent unnecessary flush for the Ethernet device output port Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 06/10] port: rework the ring output port behavior to non-blocking Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 07/10] port: free buffered packets on ring output port free Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 08/10] port: prevent unnecessary flush for the ring output port Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 09/10] examples/pipeline: print the output port packet drop counters Cristian Dumitrescu
2022-08-05 22:00 ` [PATCH 10/10] net/softnic: " Cristian Dumitrescu
2022-09-22 14:58 ` [PATCH 00/10] port: implement output port non-blocking behavior Thomas Monjalon

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=20220805220029.1096212-1-cristian.dumitrescu@intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.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 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).