| To: | Laurent DENIEL <laurent.deniel@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating master'ssettings toslaves |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 11 Aug 2003 22:32:59 -0400 |
| Cc: | Jeff Garzik <jgarzik@xxxxxxxxx>, shmulik.hen@xxxxxxxxx, bonding-devel@xxxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <3F37D2ED.B4B9223C@thalesatm.com> |
| Organization: | jamalopolis |
| References: | <E791C176A6139242A988ABA8B3D9B38A014C9474@hasmsx403.iil.intel.com> <200308111720.38472.shmulik.hen@intel.com> <1060612481.1034.15.camel@jzny.localdomain> <200308111925.38278.shmulik.hen@intel.com> <3F37C7C3.7070807@pobox.com> <3F37D2ED.B4B9223C@thalesatm.com> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 2003-08-11 at 13:31, Laurent DENIEL wrote: > But I agree that it is interesting to do some stuff at user land, and if > the bonding had an option to disable the automatic failover policy, > this could be implemented with trigger towards user land application that > could use an ioctl call to switch to the appropriate NIC according to You spoilt otherwise sane text by mentioning ioctl;-> > But the fast and simple failover policy shall remain in kernel code. nod from here. Simple failover policies should stay in the kernel. cheers, jamal |
| Previous by Date: | Re: [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating master's settings toslaves, jamal |
|---|---|
| Next by Date: | Re: [SET 2][PATCH 2/8][bonding] Propagating master's settings to slaves, jamal |
| Previous by Thread: | Re: [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating master'ssettings toslaves, jamal |
| Next by Thread: | Re: [Bonding-devel] Re: [SET 2][PATCH 2/8][bonding] Propagating master's settings toslaves, Mark Huth |
| Indexes: | [Date] [Thread] [Top] [All Lists] |