From: John Crispin <john@phrozen.org>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
John Crispin <john@phrozen.org>
Subject: [RFC 1/2] net-next: add a dma_desc element to struct skb_shared_info
Date: Fri, 21 Jul 2017 17:20:34 +0200 [thread overview]
Message-ID: <20170721152035.6645-2-john@phrozen.org> (raw)
In-Reply-To: <20170721152035.6645-1-john@phrozen.org>
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()
--
2.11.0
next prev parent reply other threads:[~2017-07-21 15:22 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 ` John Crispin [this message]
2017-07-21 15:56 ` [RFC 1/2] net-next: add a dma_desc element to struct skb_shared_info Paolo Abeni
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=20170721152035.6645-2-john@phrozen.org \
--to=john@phrozen.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox