Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3 net-next 4/7] ip6tlvs: Registration of TLV handlers and parameters
Date: Thu, 22 Aug 2019 17:17:45 +0000	[thread overview]
Message-ID: <6fc3872624214c46811a27a81c13a8c7@intel.com> (raw)
In-Reply-To: <1566254665-5200-5-git-send-email-tom@herbertland.com>

> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Tom Herbert
> Sent: Monday, August 19, 2019 3:44 PM
> To: Intel-wired-lan at lists.osuosl.org
> Cc: Tom Herbert <tom@herbertland.com>; Tom Herbert
> <tom@quantonium.net>
> Subject: [Intel-wired-lan] [PATCH v3 net-next 4/7] ip6tlvs: Registration of TLV
> handlers and parameters
> 
> From: Tom Herbert <tom@quantonium.net>
> 
> Create a single TLV parameter table that holds meta information for IPv6
> Hop-by-Hop and Destination TLVs. The data structure is composed of a 256
> element array of u8's (one entry for each TLV type to allow O(1) lookup).
> Each entry provides an offset into an array of TLV proc data structures which
> follows the array of u8s. The TLV proc data structure contains parameters and
> handler functions for receiving and transmitting TLVs. The zeroth element in
> the TLV proc array provides default parameters for TLVs.
> 
> A class attribute indicates the type of extension header in which the TLV may
> be used (e.g. Hop-by-Hop options, Destination options, or Destination
> options before the routing header).
> 
> Functions are defined to manipulate entries in the TLV parameter table.
> 
> * tlv_{set|unset}_proc set a TLV proc entry (ops and parameters)
> * tlv_{set|unset}_params set parameters only
> 
> Receive TLV lookup and processing is modified to be a lookup in the TLV
> parameter table. An init table containing parameters for TLVs supported by
> the kernel is used to initialize the TLV table.
> 
> Signed-off-by: Tom Herbert <tom@herbertland.com>
> ---
>  include/net/ipeh.h         | 107 ++++++++++++++++--
>  include/net/ipv6.h         |   3 +
>  include/uapi/linux/ipeh.h  |  16 +++
>  net/ipv6/exthdrs.c         |  14 ++-
>  net/ipv6/exthdrs_common.c  | 271
> +++++++++++++++++++++++++++++++++++++++++----
>  net/ipv6/exthdrs_options.c |  63 +++++++----
>  6 files changed, 421 insertions(+), 53 deletions(-)  create mode 100644
> include/uapi/linux/ipeh.h

Tested-by: Andrew Bowers <andrewx.bowers@intel.com>



  reply	other threads:[~2019-08-22 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 22:44 [Intel-wired-lan] [PATCH v3 net-next 0/7] ipv6: Extension header infrastructure Tom Herbert
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 1/7] ipeh: Create exthdrs_options.c and ipeh.h Tom Herbert
2019-08-22 17:13   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 2/7] ipeh: Move generic EH functions to exthdrs_common.c Tom Herbert
2019-08-22 17:13   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 3/7] ipeh: Generic TLV parser Tom Herbert
2019-08-22 17:17   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 4/7] ip6tlvs: Registration of TLV handlers and parameters Tom Herbert
2019-08-22 17:17   ` Bowers, AndrewX [this message]
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 5/7] ip6tlvs: Add TX parameters Tom Herbert
2019-08-22 17:18   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 6/7] ip6tlvs: Add netlink interface Tom Herbert
2019-08-22 17:18   ` Bowers, AndrewX
2019-08-19 22:44 ` [Intel-wired-lan] [PATCH v3 net-next 7/7] ip6tlvs: Validation of TX Destination and Hop-by-Hop options Tom Herbert
2019-08-22 17:19   ` Bowers, AndrewX

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=6fc3872624214c46811a27a81c13a8c7@intel.com \
    --to=andrewx.bowers@intel.com \
    --cc=intel-wired-lan@osuosl.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