[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DE7EF05.8030505@gmail.com>
Date: Thu, 02 Jun 2011 22:13:57 +0200
From: Nicolas de Pesloüan
<nicolas.2p.debian@...il.com>
To: David Miller <davem@...emloft.net>
CC: nhorman@...driver.com, bhutchings@...arflare.com,
netdev@...r.kernel.org, fubar@...ibm.com, andy@...yhouse.net
Subject: Re: [PATCH] bonding: reset queue mapping prior to transmission to
physical device
Le 02/06/2011 22:04, David Miller a écrit :
> From: Neil Horman<nhorman@...driver.com>
> Date: Thu, 2 Jun 2011 15:46:21 -0400
>
>> Potentially, yes. I only fixed this because I was looking at bonding and its
>> queue_mapping behavior, and saw that this needed fixing. Bridging and IP
>> forwarding should also likely clear the queue mapping in the forwarding path
>> somewhere to avoid selecting an output tx queue that is a function of whatever
>> queue and device it arrived on during ingress. I've not yet looked to see if
>> thats already being done.
>
> No we do not do this, intentionally.
>
> That way the input classification and queue selection is mirrored
> on the transmit side, which we absolutely want to happen.
Can you confirm that this is the expected behavior for IP forwarding and bridge but not for bonding?
To be more precise, due to the way bonding use queue mapping for slave selection, it is desirable to
clear the mapping before sending to the slave, because the meaning of the mapping for the slave
interface might be really different from the meaning for the bonding interface. Arguably, this is
the mapping usage in bonding which is "different" from other usages, but...
Nicolas.
--
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