From: jiangtao.jit@gmail.com (jiangtao.jit)
To: kernelnewbies@lists.kernelnewbies.org
Subject: problem with queue numbers between bridge, bonding and lo devices
Date: Mon, 25 Jul 2011 19:16:22 +0800 [thread overview]
Message-ID: <201107251916201255199@gmail.com> (raw)
In-Reply-To: CAHnt0GUBZBHyjmM6oLLLcROJHW3=2NGVfOVYJH7KjgLq4xpZAQ@mail.gmail.com
Peter:
Thanks for your urls
it very helpful and i found CS378 is suit for me
i'm working on it
2011-07-25
jiangtao.jit
???? Peter Teoh
????? 2011-07-21 11:05:21
???? jiangtao.jit
??? kernelnewbies
??? Re: Re: problem with queue numbers between bridge, bonding and lo devices
Just a few more top results from Google:
PDF] Linux Networking Kernel
www.ecsl.cs.sunysb.edu/elibrary/linux/network/LinuxKernel.pdf
File Format: PDF/Adobe Acrobat - Quick View
Linux Networking Kernel. Version 0.1. February, 12, 2003 ... This report tries to describe the Networking part of the linux networking kernel. We try ...
You visited this page on 7/21/11.
CS378 (Spring 03): Linux Kernel Programming
www.cs.utexas.edu/users/ygz/378-03S/ - Cached
CS378 Linux Kernel Programming (Spring 03). MF 12:00-1:30P ... Mar/17 M, 16: Linux Networking, Group Project 4 due. Mar/21 F, 17: Linux Networking ...
[PDF] Linux Kernel Networking
www.cs.illinois.edu/~caesar/courses/CS598.S11/.../raoul_kernel_slides.pdf
File Format: PDF/Adobe Acrobat - Quick View
User Space and Kernel Space. ?. Running Context in the Kernel. ?. Locking. ?. Deferring Work. ?. Linux Network Architecture ...
[PDF] Network Operations in the 2.6 Linux Kernel
courses.engr.illinois.edu/ece435/Labs/lab3_notes_kernel.pdf
File Format: PDF/Adobe Acrobat - View as HTML
Lab 3: Networks Operations in Linux Kernel. 1. Network Operations in the 2.6 ...
On Tue, Jul 19, 2011 at 8:32 PM, jiangtao.jit <jiangtao.jit@gmail.com> wrote:
Peter:
Thank you for your guide
these info is really helpful for me
i'll trying to learn more about networking
2011-07-19
jiangtao.jit
???? Peter Teoh
????? 2011-07-19 07:37:18
???? jiangtao.jit
??? kernelnewbies
??? Re: problem with queue numbers between bridge, bonding and lo devices
On Sat, Jul 16, 2011 at 9:04 PM, jiangtao.jit <jiangtao.jit@gmail.com> wrote:
Hi, all
recently, i read some of the Kernel codes
and i noticed that a bridge and lo device have only one queue when allocated
but a bonding device can have multi queues
they are all virtual devices
why they can have diffrent queue numbers
it confused me a lot
i would really appreciate if someone could give me some guidelines
thanks very much
what is the purpose of a "queue"? reading the documentation:
http://www.kernel.org/doc/Documentation/networking/bonding.txt
each queue correspond to each physical interface "ethX". and as all these "slave" interfaces share the same MAC address, packets can be sent out through any of these interface and received via another - allowing redundancies in terms of physical links. multiple interfaces in the same multi-queue all share the same MAC address.
but the case of bridging is not really for load balancing purposes. "bridge" literally means bridging two different physical interface, so that network traffic can hop from one to the other (independent or ignorant of L3 protocol). each physical interface must have different MAC address, so that each "queue" is actually ONE interface.
See:
http://www.youtube.com/watch?v=luOFxh1awiA&feature=related
2011-07-16
jiangtao.jit
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
Regards,
Peter Teoh
--
Regards,
Peter Teoh
prev parent reply other threads:[~2011-07-25 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 13:04 problem with queue numbers between bridge, bonding and lo devices jiangtao.jit
2011-07-18 23:37 ` Peter Teoh
2011-07-19 12:32 ` jiangtao.jit
2011-07-21 3:05 ` Peter Teoh
2011-07-25 11:16 ` jiangtao.jit [this message]
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=201107251916201255199@gmail.com \
--to=jiangtao.jit@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.