From: David Miller <davem@davemloft.net>
To: john@phrozen.org
Cc: pabeni@redhat.com, edumazet@google.com,
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 20:21:13 +0100 (WEST) [thread overview]
Message-ID: <20170721.202113.583238690576835181.davem@davemloft.net> (raw)
In-Reply-To: <6bcc6463-c2e7-5f56-22b0-f49bb369ce1c@phrozen.org>
From: John Crispin <john@phrozen.org>
Date: Fri, 21 Jul 2017 19:01:57 +0200
> When the flow offloading engine forwards a packet to the DMA it will
> send additional info to the sw path. this includes
> * physical switch port
> * internal flow hash - this is required to populate the correct flow
> * table entry
> * ppe state - this indicates what state the PPEs internal table is in
> * for the flow
> * the reason why the packet was forwarde - these are things like bind,
> * unbind, timed out, ...
>
> once the flow table offloading patches are ready and upstream, the
> netfilter layer will see the SKB and pass it o to the flow table
> offloading code, at which point it will finally end up inside the
> offloading driver. this will need to have access to this info sent to
> the sw path inside the rx descriptor to properly work out what state
> the flow is in and which table entry to populate in the HW table for
> offloading to work.
You absolutely must justify any change to a core data structure
alongside the complete and full set of patches that actually make use
of that data structure change.
You can't just say "here is the data structure change and BTW what
actually uses this is somewhere else, and not here on the list yet."
That makes it impossible to 1) evaluate the correctness of your change
and 2) validate the actual use so we can suggest alternative schemes
and/or approaches.
So please don't suggest changes this way.
Thanks.
next prev parent reply other threads:[~2017-07-21 19:21 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
2017-07-21 17:01 ` John Crispin
2017-07-21 19:21 ` David Miller [this message]
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=20170721.202113.583238690576835181.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®