Skip to contentSkip to conversation

problem with queue numbers between bridge, bonding and lo devices

DISCUSSION jiangtao.jit 2 participants 5 messages Jul 16, 2011 – Jul 25, 2011

lore
Share & tools
lore
#0 lore raw

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

2011-07-16

jiangtao.jit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110716/55beab34/attachment.html

#1 lore raw
Quoted 15 lines · jiangtao.jit

**
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

<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

<http://www.youtube.com/watch?v=luOFxh1awiA&feature=related>

Quoted 12 lines

2011-07-16
------------------------------
jiangtao.jit

_______________________________________________
Kernelnewbies mailing list Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Signature · 5 lines
Regards,
Peter Teoh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110719/d3adc566/attachment.html 
#2 lore raw

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 <[email protected]> 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

Signature · 2 lines
Regards,
Peter Teoh
#3 lore raw

Just a few more top results from Google:

1.
2. PDF] *Linux Networking
Kernel*<http://www.ecsl.cs.sunysb.edu/elibrary/linux/network/LinuxKernel.pdf>
www.ecsl.cs.sunysb.edu/elibrary/*linux*/*network*/*LinuxKernel*.pdf
File Format: PDF/Adobe Acrobat - Quick
View<http://docs.google.com/viewer?a=v&q=cache:rPjsDeXMwX4J:www.ecsl.cs.sunysb.edu/elibrary/linux/network/LinuxKernel.pdf+site:edu+linux+network+kernel&hl=en&pid=bl&srcid=ADGEESjbe8Z2URFw5UVSwywP7yHT9n8RsezQIDPbPpZDRwLy_VXiV1EuY7cFeoqO9wYVB8nsY8EYsabzFk3b7yNp1LBQK490GrzWNcaTs-Oj9xJaVNg5xhj04-sXkjQcZMp2mobveUn5&sig=AHIEtbSWXp4miewJqdrcaUOawia3aOYxnA>
*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.
3.
CS378 (Spring 03): *Linux Kernel*
Programming<http://www.cs.utexas.edu/users/ygz/378-03S/>
www.cs.utexas.edu/users/ygz/378-03S/ -
Cached<http://webcache.googleusercontent.com/search?q=cache:WVgIqgkOU3AJ:www.cs.utexas.edu/users/ygz/378-03S/+site:edu+linux+network+kernel&cd=2&hl=en&ct=clnk&source=www.google.com>
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* *...*
4.
[PDF] *Linux Kernel
Networking*<http://www.cs.illinois.edu/~caesar/courses/CS598.S11/slides/raoul_kernel_slides.pdf>
www.cs.illinois.edu/~caesar/courses/CS598.S11/.../raoul_*kernel*
_slides.pdf
File Format: PDF/Adobe Acrobat - Quick
View<http://docs.google.com/viewer?a=v&q=cache:4CLlPrhKgE8J:www.cs.illinois.edu/~caesar/courses/CS598.S11/slides/raoul_kernel_slides.pdf+site:edu+linux+network+kernel&hl=en&pid=bl&srcid=ADGEESjx6BIUgUseVN9FgNr0yUl16tRCDvmEBeVPbAu6zPmrlmtlxRWJj60MSggNSd8z4grxSCR8nTZBo7RT3UOCE2aedUT4SnBx-f6B5TA849kJA5SZ9fXaZ7gFtAlHh9ULO7zEBaL-&sig=AHIEtbQxihNgeGeylYvCZgZ6aBUjryWnJg>
User Space and *Kernel* Space. ?. Running Context in the *Kernel*. ?.
Locking. ?. Deferring Work. ?. *Linux Network* Architecture *...*
5.
[PDF] *Network* Operations in the 2.6 *Linux
Kernel*<http://courses.engr.illinois.edu/ece435/Labs/lab3_notes_kernel.pdf>
courses.engr.illinois.edu/ece435/Labs/lab3_notes_*kernel*.pdf
File Format: PDF/Adobe Acrobat - View as
HTML<http://webcache.googleusercontent.com/search?q=cache:iGcAb6FiPjQJ:courses.engr.illinois.edu/ece435/Labs/lab3_notes_kernel.pdf+site:edu+linux+network+kernel&cd=4&hl=en&ct=clnk&source=www.google.com>
Lab 3: *Networks* Operations in *Linux Kernel*. 1. *Network* Operations
in the 2.6 *...*

Quoted 86 lines · jiangtao.jit

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 <[email protected]> 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

Signature · 5 lines
Regards,
Peter Teoh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110721/86db2175/attachment-0001.html 
#4 lore raw

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 <[email protected]> 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 <[email protected]> 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

Signature · 2 lines
Regards,
Peter Teoh