All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Kierdelewicz <marek@piasta.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: big problem with HTB/CBQ and CPU for more than
Date: Tue, 29 May 2007 06:33:50 +0000	[thread overview]
Message-ID: <20070529083350.2a7dcd78@catlap> (raw)
In-Reply-To: <20070529032617.5CB6A634B3@outpost.ds9a.nl>

>So, what do you think should i do with my e1000? What do you think
>could be the best board for sites as 8.000 customers? My problem is
>exact these lots of interruptions.

Plug as many network interfaces (e1000) as cpu cores you have. E1000
multiport nics have separate irq assigned to each "port", so having 2 x
Quad-Core Xeon and 2 x 4-port e1000 would allow you to configure static
affinity of each port to one core:
http://bcr2.uwaterloo.ca/~brecht/servers/apic/SMP-affinity.txt

Sometimes symmetric usage of network interfaces (for symmetric
core usage) is the problem. I think you can achieve it by plugging all 8
ports to managed switch and configuring some form of aggregation. The
best would be src/dst IP EtherChannel or something similar. For some
deployments (where router sees all the clients on OSI layer 2) src/dst
MAC EtherChannel would suffice. On linux side you would have to
configure bonding:
http://linux-net.osdl.org/index.php/Bonding

pozdrawiam,
Marek Kierdelewicz
KoBa ISP
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2007-05-29  6:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 23:25 [LARTC] Re: big problem with HTB/CBQ and CPU for more than 1.700 Pablo Fernandes Yahoo
2007-05-29  6:33 ` Marek Kierdelewicz [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=20070529083350.2a7dcd78@catlap \
    --to=marek@piasta.pl \
    --cc=lartc@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.