From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: netdev@vger.kernel.org, lorenzo.bianconi@redhat.com,
davem@davemloft.net, kuba@kernel.org, brouer@redhat.com,
echaudro@redhat.com, john.fastabend@gmail.com
Subject: Re: [PATCH net-next 0/3] mvneta: access skb_shared_info only on last frag
Date: Fri, 20 Nov 2020 15:10:32 -0800 [thread overview]
Message-ID: <20201120151032.00006bd2@intel.com> (raw)
In-Reply-To: <cover.1605889258.git.lorenzo@kernel.org>
Lorenzo Bianconi wrote:
> Build skb_shared_info on mvneta_rx_swbm stack and sync it to xdp_buff
> skb_shared_info area only on the last fragment.
> Avoid avoid unnecessary xdp_buff initialization in mvneta_rx_swbm routine.
> This a preliminary series to complete xdp multi-buff in mvneta driver.
>
> Lorenzo Bianconi (3):
> net: mvneta: avoid unnecessary xdp_buff initialization
> net: mvneta: move skb_shared_info in mvneta_xdp_put_buff
> net: mvneta: alloc skb_shared_info on the mvneta_rx_swbm stack
>
> drivers/net/ethernet/marvell/mvneta.c | 55 +++++++++++++++++----------
> 1 file changed, 35 insertions(+), 20 deletions(-)
>
For the series:
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
next prev parent reply other threads:[~2020-11-20 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 17:05 [PATCH net-next 0/3] mvneta: access skb_shared_info only on last frag Lorenzo Bianconi
2020-11-20 17:05 ` [PATCH net-next 1/3] net: mvneta: avoid unnecessary xdp_buff initialization Lorenzo Bianconi
2020-11-20 17:05 ` [PATCH net-next 2/3] net: mvneta: move skb_shared_info in mvneta_xdp_put_buff caller Lorenzo Bianconi
2020-11-20 17:05 ` [PATCH net-next 3/3] net: mvneta: alloc skb_shared_info on the mvneta_rx_swbm stack Lorenzo Bianconi
2020-11-20 23:10 ` Jesse Brandeburg [this message]
2020-11-24 20:26 ` [PATCH net-next 0/3] mvneta: access skb_shared_info only on last frag Jakub Kicinski
2020-11-24 22:18 ` Lorenzo Bianconi
2020-11-24 22:25 ` Daniel Borkmann
2020-11-24 22:30 ` Jakub Kicinski
2020-11-24 23:00 ` Daniel Borkmann
2020-11-24 23:10 ` Jakub Kicinski
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=20201120151032.00006bd2@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=echaudro@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.