[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170821115106.70fa1e1d@griffin>
Date: Mon, 21 Aug 2017 11:51:06 +0200
From: Jiri Benc <jbenc@...hat.com>
To: Jan Scheurich <jan.scheurich@...csson.com>
Cc: "Yang, Yi" <yi.y.yang@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"dev@...nvswitch.org" <dev@...nvswitch.org>,
"blp@....org" <blp@....org>, "e@...g.me" <e@...g.me>
Subject: Re: [PATCH net-next v4] openvswitch: enable NSH support
On Mon, 21 Aug 2017 09:42:27 +0000, Jan Scheurich wrote:
> I understand your concern. But not declaring md2 as array is wrong as
> well, as there might not be an MD2 TLV context header. An MD2 NSH
> header is perfectly valid without any TLV. So in any case the user of
> the struct needs to be aware of the NSH semantics.
Good point.
> NSH can be carried over Ethernet with a 14 byte header. In that case
> the total NSH header would typically be 16-bit aligned, so that all
> 32-bit members would be misaligned.
See NET_IP_ALIGN in include/linux/skbuff.h.
Jiri
Powered by blists - more mailing lists