netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Majid Khan" <majidkk@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Netfilter and SMP
Date: Fri, 26 May 2006 19:52:50 +0200	[thread overview]
Message-ID: <200605261952.50755.ak@suse.de> (raw)
In-Reply-To: <a656c20605260823o1c894411t88a76c23d7855406@mail.gmail.com>


> Can somebody provide me with some information on how to configure my
> SMP system so that both processors share the network traffic load.

You would need multiple active incoming network interfaces. 
Linux right now doesn't support load balancing from a single interrupt.
Even if it did that would likely require hardware support for MSI-X.

> My second question was that if there is any known method to gracefully
> handle failures in a netfilter module. Currently any failure in
> netfilter would cause the kernel panic.

Write a user space module using nf queue? 

-Andi
 

      reply	other threads:[~2006-05-26 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26 15:23 Netfilter and SMP Majid Khan
2006-05-26 17:52 ` Andi Kleen [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=200605261952.50755.ak@suse.de \
    --to=ak@suse.de \
    --cc=majidkk@gmail.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).