[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <511F6FF1.9000004@linux-ipv6.org>
Date: Sat, 16 Feb 2013 20:39:29 +0900
From: YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
To: Eric Dumazet <eric.dumazet@...il.com>
CC: netdev@...r.kernel.org, davem@...emloft.net,
Ben Greear <greearb@...delatech.com>,
Vlad Yasevich <vyasevic@...hat.com>,
YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
Subject: Re: [RFC PATCH net-next (V2)] ipv6: Queue fragments per interface
for multicast/link-local addresses.
Eric Dumazet wrote:
> On Sat, 2013-02-16 at 14:49 +0900, YOSHIFUJI Hideaki wrote:
>> We should queue fragments for the same link-local address on
>> different interfaces (e.g. fe80::1%eth0 and fe80::1%eth1) to the
>> different queue, because of nature of addressing architecture.
>>
>> Similarly, we should queue fragments for multicast on different
>> interface to the different queue. This is okay because
>> application joins group on speicific interface, and multicast
>> traffic is expected only on that interface.
>>
>> CC: Ben Greear <greearb@...delatech.com>
>> CC: Vlad Yasevich <vyasevic@...hat.com>
>> CC: Eric Dumazet <eric.dumazet@...il.com>
>> Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
>> ---
>
> I would definitely ask advice from Patrick & Pablo on this patch.
>
> If a router uses several links in aggregation (but no bonding dev), we
> might break fragmentation/reassembly.
Could you elaborate, please?
The patch does not compare incoming interface if address is
non-link-local unicast address.
--yoshfuji
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists