From: Jay Vosburgh <fubar@us.ibm.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] quick help with bonding?
Date: Thu, 29 Mar 2007 09:24:00 -0700 [thread overview]
Message-ID: <22707.1175185440@death> (raw)
In-Reply-To: <460BE5F0.7070606@nortel.com>
Chris Friesen <cfriesen@nortel.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@us.ibm.com
next prev parent reply other threads:[~2007-03-29 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 16:14 quick help with bonding? Chris Friesen
2007-03-29 16:24 ` Jay Vosburgh [this message]
2007-03-29 18:16 ` [Bonding-devel] " Andy Gospodarek
2007-03-29 22:08 ` Chris Friesen
2007-03-29 22:30 ` Jay Vosburgh
2007-03-29 23:01 ` Mark Huth
2007-03-29 23:42 ` Chris Friesen
2007-03-30 0:13 ` Jay Vosburgh
2007-03-30 0:36 ` Andy Gospodarek
2007-03-30 1:19 ` Chris Friesen
2007-03-30 1:26 ` Chris Friesen
2007-03-30 2:48 ` Andy Gospodarek
2007-03-30 2:49 ` Chris Friesen
2007-04-02 22:28 ` Chris Friesen
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=22707.1175185440@death \
--to=fubar@us.ibm.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=cfriesen@nortel.com \
--cc=netdev@vger.kernel.org \
/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).