netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paweł Staszewski" <pstaszewski@itcare.pl>
To: Patrick McHardy <kaber@trash.net>
Cc: Linux Network Development list <netdev@vger.kernel.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: [ SPAM ] Re: Is this normal?
Date: Tue, 27 Jan 2009 15:26:08 +0100	[thread overview]
Message-ID: <497F1980.1070008@itcare.pl> (raw)
In-Reply-To: <497F16F7.6020504@trash.net>

Patrick McHardy pisze:
> Paweł Staszewski wrote:
>> I have Linux that works as Router + traffic management with 
>> connection tracking enabled but without making NAT
>>
>> About 600Mbit/s TX and 600Mbit/s RX forwarded traffic
>>
>> iptables -L -n -v -t raw
>> Chain PREROUTING (policy ACCEPT 3340M packets, 2623G bytes)
>> pkts bytes target     prot opt in     out     source               
>> destination
>> 3339M 2621G NOTRACK    all  --  *      *       0.0.0.0/0            
>> 0.0.0.0/0
>>
>>
>> kernel 2.6.28.2
>> CPU: Core 2, speed 2999.98 MHz (estimated)
>> Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a 
>> unit mask of 0x00 (Unhalted core cycles) count 100000
>> samples  %        image name               app name                 
>> symbol name
>> 14544205 15.8604  vmlinux                  vmlinux                  
>> ctnetlink_del_expect
>
> This doesn't seem to be accurate, I'm guessing its really
> ctnetlink_conntrack_event().
>
> Does this patch make any difference?

I will check this patch today at night.


  reply	other threads:[~2009-01-27 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <497F14B1.7070306@itcare.pl>
2009-01-27 14:15 ` Is this normal? Patrick McHardy
2009-01-27 14:26   ` Paweł Staszewski [this message]
2009-01-28 16:09   ` [ SPAM ] " Paweł Staszewski

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=497F1980.1070008@itcare.pl \
    --to=pstaszewski@itcare.pl \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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).