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 0/2] net-next: hw flow offloading
Date: Fri, 21 Jul 2017 17:20:33 +0200 [thread overview]
Message-ID: <20170721152035.6645-1-john@phrozen.org> (raw)
Hi,
I managed to bring up the flow offloading on latest MedieTek silicon.
When enabling HW flow offloading, the traffic coming in on either of the
GMACs is first sent to the PPE for processing. Any traffic not offloaded
at this point will then be forwarded to the normal RX DMA ring for SW path
processing. In this case the PPE will send additional data inside RXD4
that is later required by the upper layers to populate the flow offloading
engines HW tables properly.
This series is a RFC as i am not sure how to best propagate the additional
info from the RX DMA descriptor. The driver is still using NF hooks and
I plan to rebase it and send it upstream once the flow table offloading
patches that folks are working on are upstream.
I am right now trying to get rid of the remaning hacks in the code and
wanted to know if this series would be a feasible solution.
John
John Crispin (2):
net-next: add a dma_desc element to struct skb_shared_info
net-next: mediatek: populate the shared
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 4 ++++
include/linux/skbuff.h | 1 +
2 files changed, 5 insertions(+)
--
2.11.0
next 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 John Crispin [this message]
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
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-1-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