Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Sep 2014 18:49:27 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        Rui Paulo <rpaulo@me.com>
Cc:        "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>
Subject:   Re: svn commit: r271297 - head/sys/netinet
Message-ID:  <CAJ-VmomQRB0-07voRy0uhGKXzmz%2BVexzA5Sn8QXF2qrOtZs2zA@mail.gmail.com>
In-Reply-To: <BFAF1862-480C-430B-BC63-E209E77D8E1A@me.com>
References:  <201409090310.s893ALba076415@svn.freebsd.org> <BFAF1862-480C-430B-BC63-E209E77D8E1A@me.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 15 September 2014 17:00, Rui Paulo <rpaulo@me.com> wrote:
> On Sep 8, 2014, at 20:10, Adrian Chadd <adrian@FreeBSD.org> wrote:
>>
>>  The IPv6 part of this is missing - I'm going to do some re-juggling of
>>  where various parts of the RSS framework live before I add the IPv6
>>  code (read: the IPv6 code is going to go into netinet6/in6_rss.[ch],
>>  rather than living here.)
>
> Any thoughts on how are you going to handle the IPv6 part?  I would probably avoid parsing any special IPv6 header type and provide RSS iff the packet is IPv6 header + next header = (TCP|UDP).

I'm likely going to do exactly that for now and only support those
bits in the RSS config. The IPV6 _EXT bits can come later.


-a



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomQRB0-07voRy0uhGKXzmz%2BVexzA5Sn8QXF2qrOtZs2zA>