All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: Completely DROP for UDP packets.
Date: Mon, 10 Dec 2007 16:17:31 +0100	[thread overview]
Message-ID: <475D588B.9040205@plouf.fr.eu.org> (raw)
In-Reply-To: <4988.211.111.195.128.1197265533.squirrel@211.111.194.2>

Hello,

msn a écrit :
> 
> So, it is NOT possible to decreasing the CPU usage of the massive UDP
> handling in the linux kernel ? any comments would be nice to me.

You cannot decrease the packet processing load in the network interface 
driver, unless you use a more "efficient" network card or driver. As 
Martijn wrote, the best you can do at iptables level is drop the packets 
as soon as possible, in the PREROUTING chain of the 'raw' table even 
though this is not the primary purpose of the 'raw' table. This will 
save CPU usage for the traversal of subsequent iptables chains, the 
connection tracking if it is enabled (as opposed to filtering in the 
PREROUTING chain of the 'mangle' table), the input routing decision and 
the fragment reassembly (as opposed to filtering in the INPUT chain of 
any table).

The path is as follows :

interface -> raw/PREROUTING -> conntrack & fragment reassembly -> 
mangle/PREROUTING -> nat/PREROUTING -> routing decision -> fragment 
reassembly -> mangle/INPUT -> filter/INPUT -> local delivery

      reply	other threads:[~2007-12-10 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08 19:39 Completely DROP for UDP packets msn
2007-12-08 20:34 ` Martijn Lievaart
2007-12-10  5:43   ` msn
2007-12-10  5:45   ` msn
2007-12-10 15:17     ` Pascal Hambourg [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=475D588B.9040205@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --cc=netfilter@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.