From: Paolo Abeni <pabeni@redhat.com>
To: John Crispin <john@phrozen.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC 1/2] net-next: add a dma_desc element to struct skb_shared_info
Date: Fri, 21 Jul 2017 17:56:39 +0200 [thread overview]
Message-ID: <1500652599.3924.10.camel@redhat.com> (raw)
In-Reply-To: <20170721152035.6645-2-john@phrozen.org>
Hi,
On Fri, 2017-07-21 at 17:20 +0200, John Crispin wrote:
> In order to make HW flow offloading work in latest MediaTek silicon we need
> to propagate part of the RX DMS descriptor to the upper layers populating
> the flow offload engines HW tables. This patch adds an extra element to
> struct skb_shared_info allowing the ethernet drivers RX napi code to store
> the required information and make it persistent for the lifecycle of the
> skb and its clones.
>
> Signed-off-by: John Crispin <john@phrozen.org>
> ---
> include/linux/skbuff.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index 4093552be1de..db9576cd946b 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -426,6 +426,7 @@ struct skb_shared_info {
> unsigned int gso_type;
> u32 tskey;
> __be32 ip6_frag_id;
> + u32 dma_desc;
>
> /*
> * Warning : all fields before dataref are cleared in __alloc_skb()
This will increase the skb_shared_info struct size, which is already
quite large, and can have several kind of performance drawback.
AFAIK this is discouraged.
I don't understand the use case; the driver will set this field, but
who is going to consume it?
Thanks,
Paolo
next prev parent reply other threads:[~2017-07-21 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 15:20 [RFC 0/2] net-next: hw flow offloading John Crispin
2017-07-21 15:20 ` [RFC 1/2] net-next: add a dma_desc element to struct skb_shared_info John Crispin
2017-07-21 15:56 ` Paolo Abeni [this message]
2017-07-21 17:01 ` John Crispin
2017-07-21 19:21 ` David Miller
2017-07-21 20:37 ` Florian Westphal
2017-07-21 15:20 ` [RFC 2/2] net-next: mediatek: populate the shared John Crispin
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=1500652599.3924.10.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.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.