From: John Fastabend <john.fastabend@gmail.com>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Anjali Singhai Jain <anjali.singhai@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
ast@fb.com, "Skidmore, Donald C" <donald.c.skidmore@intel.com>,
horms@verge.net.au, Linux Netdev List <netdev@vger.kernel.org>,
Thomas Graf <tgraf@suug.ch>, David Miller <davem@davemloft.net>
Subject: Re: [RFC PATCH 6/7] net: ixgbe: add minimal parser details for ixgbe
Date: Tue, 02 Feb 2016 08:46:44 -0800 [thread overview]
Message-ID: <56B0DD74.1090806@gmail.com> (raw)
In-Reply-To: <CAJ3xEMi_4N-x=_jKaJ8_f2BxHhrhhiCuftwzmqNZaiGv_d1c9w@mail.gmail.com>
On 16-02-02 08:27 AM, Or Gerlitz wrote:
> On Mon, Feb 1, 2016 at 3:52 AM, John Fastabend <john.fastabend@gmail.com> wrote:
>> This adds an ixgbe data structure that is used to determine what
>> headers:fields can be matched and in what order they are supported.
>>
>> For hardware devices this can be a bit tricky because typically
>> only pre-programmed (firmware, ucode, rtl) parse graphs will be
>> supported and we don't yet have an interface to change these from
>> the OS. So its sort of a you get whatever your friendly vendor
>> provides affair at the moment.
>>
>> In the future we can add the get routines and set routines to
>> update this data structure. One interesting thing to note here
>> is the data structure here identifies ethernet, ip, and tcp
>> fields without having to hardcode them as enumerations or use
>> other identifiers.
>
> Maybe for the current state this patch (or the most of it) can be
> made generic and provided in a way that multiple HW drivers can use it?
>
If you want the structs we can put them in a helper lib but the
main code is two for loops to catch the keys and an if block to catch
the nexthdr code mixed with a bunch of code to program the specific
device. Its just not that helpful to other drivers.
.John
next prev parent reply other threads:[~2016-02-02 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 1:48 [RFC PATCH 0/7] tc cls_u32 hardware interface John Fastabend
2016-02-01 1:49 ` [RFC PATCH 1/7] net: rework ndo tc op to consume additional qdisc handle parameter John Fastabend
2016-02-01 1:49 ` [RFC PATCH 2/7] net: rework setup_tc ndo op to consume general tc operand John Fastabend
2016-02-01 1:50 ` [RFC PATCH 3/7] net: sched: add cls_u32 offload hooks for netdevs John Fastabend
2016-02-02 16:25 ` Or Gerlitz
2016-02-02 16:42 ` John Fastabend
2016-02-02 22:06 ` Or Gerlitz
2016-02-01 1:51 ` [RFC PATCH 4/7] net: add tc offload feature flag John Fastabend
2016-02-01 1:51 ` [RFC PATCH 5/7] net: tc: helper functions to query action types John Fastabend
2016-02-01 1:52 ` [RFC PATCH 6/7] net: ixgbe: add minimal parser details for ixgbe John Fastabend
2016-02-02 16:27 ` Or Gerlitz
2016-02-02 16:46 ` John Fastabend [this message]
2016-02-01 1:53 ` [RFC PATCH 7/7] net: ixgbe: add support for tc_u32 offload John Fastabend
2016-02-02 2:17 ` David Miller
2016-02-02 4:53 ` John Fastabend
2016-02-02 11:49 ` [RFC PATCH 0/7] tc cls_u32 hardware interface Jiri Pirko
2016-02-02 14:58 ` John Fastabend
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=56B0DD74.1090806@gmail.com \
--to=john.fastabend@gmail.com \
--cc=anjali.singhai@intel.com \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=gerlitz.or@gmail.com \
--cc=horms@verge.net.au \
--cc=jesse.brandeburg@intel.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).