From: John Fastabend <john.fastabend@gmail•com>
To: Jiri Pirko <jiri@resnulli•us>
Cc: sfeldma@gmail•com, netdev@vger•kernel.org, davem@davemloft•net,
f.fainelli@gmail•com, roopa@cumulusnetworks•com
Subject: Re: [RFC PATCH net-next 0/2] Add new switchdev device class
Date: Thu, 27 Aug 2015 01:09:27 -0700 [thread overview]
Message-ID: <55DEC5B7.5040505@gmail.com> (raw)
In-Reply-To: <20150827074418.GL2228@nanopsycho.orion>
[...]
>>
>> The structure I used previously which looks like your prototype I think,
>>
>> (https://github.com/jrfastab/rocker-net-next/blob/master/include/uapi/linux/if_flow.h)
>>
>> * [NFL_TABLE_IDENTIFIER_TYPE]
>> * [NFL_TABLE_IDENTIFIER]
>> * [NFL_TABLE_TABLES]
>> * [NFL_TABLE]
>> * [NFL_TABLE_ATTR_NAME]
>> * [NFL_TABLE_ATTR_UID]
>> * [NFL_TABLE_ATTR_SOURCE]
>> * [NFL_TABLE_ATTR_APPLY]
>> * [NFL_TABLE_ATTR_SIZE]
>> * [NFL_TABLE_ATTR_MATCHES]
>> * [NFL_FIELD_REF]
>> * [NFL_FIELD_REF_INSTANCE]
>> * [NFL_FIELD_REF_HEADER]
>> * [NFL_FIELD_REF_FIELD]
>> * [NFL_FIELD_REF_MASK]
>> * [NFL_FIELD_REF_TYPE]
>> * [...]
>> * [NFL_TABLE_ATTR_ACTIONS]
>> * [NFL_ACTION_ATTR_UID]
>> * [...]
>> * [NFL_TABLE]
>> * [...]
>> *
>>
>> This is well-typed per Dave's comment. And because its Netlink based it
>> can be easily extended as needed. The above gives basic information on
>> the table. Sure it could stand to have some other entries in it but I
>> never needed them for my capabilities/resource discovery. We could argue
>> about removing some if they are too specific to my use cases.
>
> I guess you are talking about read-only interface right?
>
Correct. read-only.
next prev parent reply other threads:[~2015-08-27 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 7:16 [RFC PATCH net-next 0/2] Add new switchdev device class sfeldma
2015-08-27 7:16 ` [RFC PATCH net-next 1/2] switchdev: create " sfeldma
2015-08-27 7:16 ` [RFC PATCH net-next 2/2] rocker: register each switch as a switchdev sfeldma
2015-08-27 7:27 ` [RFC PATCH net-next 0/2] Add new switchdev device class Jiri Pirko
2015-08-27 7:43 ` John Fastabend
2015-08-27 7:51 ` Jiri Pirko
2015-08-27 8:14 ` John Fastabend
2015-08-27 8:17 ` Scott Feldman
2015-08-27 8:41 ` Jiri Pirko
2015-08-27 7:36 ` John Fastabend
2015-08-27 7:44 ` Jiri Pirko
2015-08-27 8:09 ` John Fastabend [this message]
2015-08-27 8:23 ` Scott Feldman
2015-08-27 7:45 ` Andrew Lunn
2015-08-27 8:42 ` Scott Feldman
2015-08-27 9:06 ` Andrew Lunn
2015-08-27 16:41 ` Scott Feldman
2015-08-28 11:52 ` Andrew Lunn
2015-08-27 13:54 ` John W. Linville
2015-08-27 23:25 ` David Miller
2015-08-28 2:13 ` Arad, Ronen
2015-08-28 16:55 ` Florian Fainelli
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=55DEC5B7.5040505@gmail.com \
--to=john.fastabend@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=sfeldma@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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