netdev - Re: [Bonding-devel] quick help with bonding?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <22707.1175185440@death>
Date:	Thu, 29 Mar 2007 09:24:00 -0700
From:	Jay Vosburgh <fubar@...ibm.com>
To:	"Chris Friesen" <cfriesen@...tel.com>
cc:	netdev@...r.kernel.org, bonding-devel@...ts.sourceforge.net
Subject: Re: [Bonding-devel] quick help with bonding? 

Chris Friesen <cfriesen@...tel.com> wrote:

>Could someone either point me to the bonding high level design document 
>(couldn't find one at the sourceforge project page) or else give me a 
>quick overview of the code path followed by an incoming packet when 
>bonding is involved?

	There really isn't a high level design document.

	The input path goes from the driver, which (probably) calls
netif_receive_skb.  That function does its processing whatnot, the only
special step for bonding is the processing done by skb_bond() which
assigns the packet to the bonding device.  In the current mainline,
skb_bond() also does some stuff to drop traffic on inactive slaves as
the like.

	After that, the packet follows the regular input path in
netif_skb_receive.

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
-
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