From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3 net-next 9/9] i40e: respect metadata on XSK Rx to skb
Date: Wed, 8 Dec 2021 14:47:35 +0100 [thread overview]
Message-ID: <87463ddc-bf93-99cc-65d1-cbc215125ec3@redhat.com> (raw)
In-Reply-To: <20211207205536.563550-10-alexandr.lobakin@intel.com>
On 07/12/2021 21.55, Alexander Lobakin wrote:
> For now, if the XDP prog returns XDP_PASS on XSK, the metadata will
> be lost as it doesn't get copied to the skb.
> Copy it along with the frame headers. Account its size on skb
> allocation, and when copying just treat it as a part of the frame
> and do a pull after to "move" it to the "reserved" zone.
> net_prefetch() xdp->data_meta and align the copy size to speed-up
> memcpy() a little and better match ixgbee_costruct_skb().
^^^^^^^^^^^^^^^^^^^
Misspelling function name.
>
> Fixes: d0bcacd0a130 ("ixgbe: add AF_XDP zero-copy Rx support")
> Suggested-by: Jesper Dangaard Brouer <brouer@redhat.com>
> Suggested-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> Signed-off-by: Alexander Lobakin <alexandr.lobakin@intel.com>
> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_xsk.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
Wrong driver (i40e:) "tagged" in subject.
prev parent reply other threads:[~2021-12-08 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 20:55 [Intel-wired-lan] [PATCH v3 net-next 0/9] net: intel: napi_alloc_skb() vs metadata Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 1/9] i40e: don't reserve excessive XDP_PACKET_HEADROOM on XSK Rx to skb Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 2/9] i40e: respect metadata " Alexander Lobakin
2022-01-10 10:31 ` Bhandare, KiranX
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 3/9] ice: respect metadata in legacy-rx/ice_construct_skb() Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 4/9] ice: don't reserve excessive XDP_PACKET_HEADROOM on XSK Rx to skb Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 5/9] ice: respect metadata " Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 6/9] igc: don't reserve excessive XDP_PACKET_HEADROOM " Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 7/9] ixgbe: pass bi->xdp to ixgbe_construct_skb_zc() directly Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 8/9] ixgbe: don't reserve excessive XDP_PACKET_HEADROOM on XSK Rx to skb Alexander Lobakin
2021-12-07 20:55 ` [Intel-wired-lan] [PATCH v3 net-next 9/9] i40e: respect metadata " Alexander Lobakin
2021-12-08 13:47 ` Jesper Dangaard Brouer [this message]
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=87463ddc-bf93-99cc-65d1-cbc215125ec3@redhat.com \
--to=jbrouer@redhat.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