From: Badalian Vyacheslav <slavon@bigtelecom.ru>
To: Marek Kierdelewicz <marek@piasta.pl>, netdev@vger.kernel.org
Subject: Re: Simple question about network stack
Date: Tue, 25 Dec 2007 11:52:48 +0300 [thread overview]
Message-ID: <4770C4E0.1040708@bigtelecom.ru> (raw)
In-Reply-To: <20071224205358.5c192f8d@catlap>
Marek Kierdelewicz:
> Hi,
>
>
>> Have 2 Ethernet adapters e1000. Have 8 CPU (4 real).
>> Computer work as Shaper. Use only TC rules to shape and IPTABLES to
>> drop.
>> question:
>> 1. I may balance load to other cpu? I understand that i can't balance
>> polling place, but find in TC and IPTABLES hash may do different cpu?
>>
>
> You need as many nics as cpus to effectivelu use all your processing
> power. You can pair-up nics and cpus by configuring appropriate irq
> smp affinity. Read in [1] from line 350 on.
>
Interesting. Sorry if my questions will be stupid. "smp affinity" its
was i need, but it not work for me, and never work if i remember =(
Maybe Guru of Network ask me where i have simple stupid mistake?
In theory
#cat ffffffff > /proc/irq/ID/smp_affinity
set mask that all cpus must get interrupts RR
but i see in cat /proc/interrupts that all interrupts get only CPU0
On CPU1 0 interrupts
i do
#cat 2 > /proc/irq/16/smp_affinity
#cat 2 > /proc/irq/17/smp_affinity
#echo /proc/irq/1[67]/smp_affinity
00000002
00000002
Great. Interrupts go to CPU1
#cat 1 > /proc/irq/16/smp_affinity
#cat 1 > /proc/irq/17/smp_affinity
#echo /proc/irq/1[67]/smp_affinity
00000001
00000001
Great. Interrupts go to CPU0
#cat 3 > /proc/irq/16/smp_affinity
#cat 3 > /proc/irq/17/smp_affinity
#echo /proc/irq/1[67]/smp_affinity
00000003
00000003
Strange. Interrupts go to CPU0 only.
Where i have mistake? Why i not have RR? Or i mistake in SMP Affinity idea?
Thanks for answers!
Slavon
> Another option is to use recent e1000 nics with multiqueue capability.
> Read in [2]. Google for more information. I'm not sure but you'll
> probably need non-kerel recent e1000 drivers from sourceforge.
>
> [1]http://www.mjmwired.net/kernel/Documentation/filesystems/proc.txt
> [2]http://www.mjmwired.net/kernel/Documentation/networking/multiqueue.txt
>
> cheers,
> Marek Kierdelewicz
>
>
next prev parent reply other threads:[~2007-12-25 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 9:52 Simple question about network stack Badalian Vyacheslav
[not found] ` <20071224205358.5c192f8d@catlap>
2007-12-25 8:52 ` Badalian Vyacheslav [this message]
2007-12-25 15:41 ` Denys Fedoryshchenko
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=4770C4E0.1040708@bigtelecom.ru \
--to=slavon@bigtelecom.ru \
--cc=marek@piasta.pl \
--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 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.