Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v5 intel-next 5/9] ice: do not create xdp_frame on XDP_TX
Date: Sat, 14 Aug 2021 16:08:08 +0200	[thread overview]
Message-ID: <20210814140812.46632-6-maciej.fijalkowski@intel.com> (raw)
In-Reply-To: <20210814140812.46632-1-maciej.fijalkowski@intel.com>

xdp_frame is not needed for XDP_TX data path in ice driver case.
For this data path cleaning of sent descriptor will not happen anywhere
outside of the driver, which means that carrying the information about
the underlying memory model via xdp_frame will not be used. Therefore,
this conversion can be simply dropped, which would relieve CPU a bit.

Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
---
 drivers/net/ethernet/intel/ice/ice_txrx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/intel/ice/ice_txrx.c b/drivers/net/ethernet/intel/ice/ice_txrx.c
index 851a6e68aedf..f2e6a37112d1 100644
--- a/drivers/net/ethernet/intel/ice/ice_txrx.c
+++ b/drivers/net/ethernet/intel/ice/ice_txrx.c
@@ -552,7 +552,7 @@ ice_run_xdp(struct ice_rx_ring *rx_ring, struct xdp_buff *xdp,
 		return ICE_XDP_PASS;
 	case XDP_TX:
 		xdp_ring = rx_ring->vsi->xdp_rings[smp_processor_id()];
-		result = ice_xmit_xdp_buff(xdp, xdp_ring);
+		result = ice_xmit_xdp_ring(xdp->data, xdp->data_end - xdp->data, xdp_ring);
 		if (result == ICE_XDP_CONSUMED)
 			goto out_failure;
 		return result;
-- 
2.20.1


  parent reply	other threads:[~2021-08-14 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 14:08 [Intel-wired-lan] [PATCH v5 intel-next 0/9] XDP_TX improvements for ice Maciej Fijalkowski
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 1/9] ice: remove ring_active from ice_ring Maciej Fijalkowski
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 2/9] ice: move ice_container_type onto ice_ring_container Maciej Fijalkowski
2021-08-16 16:51   ` Creeley, Brett
2021-08-16 18:39     ` Maciej Fijalkowski
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 3/9] ice: split ice_ring onto Tx/Rx separate structs Maciej Fijalkowski
2021-08-14 16:18   ` kernel test robot
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 4/9] ice: unify xdp_rings accesses Maciej Fijalkowski
2021-08-14 14:08 ` Maciej Fijalkowski [this message]
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 6/9] ice: propagate xdp_ring onto rx_ring Maciej Fijalkowski
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 7/9] ice: optimize XDP_TX workloads Maciej Fijalkowski
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 8/9] ice: introduce XDP_TX fallback path Maciej Fijalkowski
2021-08-14 14:08 ` [Intel-wired-lan] [PATCH v5 intel-next 9/9] ice: make use of ice_for_each_* macros Maciej Fijalkowski
2021-08-17 20:59 ` [Intel-wired-lan] [PATCH v5 intel-next 0/9] XDP_TX improvements for ice Nguyen, Anthony L
2021-08-18  7:52   ` Maciej Fijalkowski
2021-08-18 14:03     ` Maciej Fijalkowski
2021-08-18 16:12       ` Nguyen, Anthony L

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=20210814140812.46632-6-maciej.fijalkowski@intel.com \
    --to=maciej.fijalkowski@intel.com \
    --cc=intel-wired-lan@osuosl.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