From: Nikolay Aleksandrov <nikolay@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, rajesh.borundia@qlogic.com,
agospoda@redhat.com, sony.chacko@qlogic.com
Subject: Re: [PATCH net-next v3] netxen: write IP address to firmware when using bonding
Date: Wed, 13 Mar 2013 11:34:23 +0100 [thread overview]
Message-ID: <5140562F.8080009@redhat.com> (raw)
In-Reply-To: <20130313.044244.2078533144108853623.davem@davemloft.net>
On 13/03/13 09:42, David Miller wrote:
> From: Nikolay Aleksandrov <nikolay@redhat.com>
> Date: Tue, 12 Mar 2013 13:49:01 +0100
>
>> This patch allows LRO aggregation on bonded devices that contain an
>> NX3031 device. It also adds a for_each_netdev_in_bond_rcu(bond, slave)
>> macro which executes for each slave that has bond as master.
>
> The new logic looks like it will configure the IPs for bonding
> but not for VLANs, is that intentional?
The case bond -> vlan -> netxen was intentionally dropped as it leads to
many new issues, if that is what you are referring to. The case vlan ->
netxen still works, since the address of orig_dev is unconditionally
programmed if the original dev is a netxen. The problem was with a bond
acting on a vlan which is configured on a netxen because we would have
to keep track of which bonding master the programmed addresses belong to.
next prev parent reply other threads:[~2013-03-13 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 12:49 [PATCH net-next v3] netxen: write IP address to firmware when using bonding Nikolay Aleksandrov
2013-03-13 8:42 ` David Miller
2013-03-13 10:34 ` Nikolay Aleksandrov [this message]
2013-03-13 11:51 ` Rajesh Borundia
2013-03-15 12:23 ` David Miller
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=5140562F.8080009@redhat.com \
--to=nikolay@redhat.com \
--cc=agospoda@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rajesh.borundia@qlogic.com \
--cc=sony.chacko@qlogic.com \
/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;
as well as URLs for NNTP newsgroup(s).