From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: [RFC SKBUFF]: Keep track of writable header len of headerless clones
Date: Mon, 25 Jun 2007 10:53:52 +0200 [thread overview]
Message-ID: <467F82A0.3070801@trash.net> (raw)
In-Reply-To: <20070624.193751.46198776.davem@davemloft.net>
David Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Sun, 24 Jun 2007 14:53:36 +0200
>
>
>> - sendmsg eth0, no NAT: sys 0m2.508s
>> - sendmsg eth0, NAT: sys 0m2.539s
>> - sendmsg eth0, NAT + patch: sys 0m2.445s (no change)
>>
>
> This is probably because we're touching all the data anyways
> and if the resident set size is small enough (as a gigabit
> or 100MB ethernet TCP stream window would be) then it all fits
> mostly in the L2 caches of the cpu.
Yeah, thats what I suspected too. On loopback it seems to exceed
the cache size, which is a bit strange since its 1MB. Or maybe
there is some loopback optimization interfering.
next prev parent reply other threads:[~2007-06-25 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 12:53 [RFC SKBUFF]: Keep track of writable header len of headerless clones Patrick McHardy
2007-06-25 2:37 ` David Miller
2007-06-25 8:53 ` Patrick McHardy [this message]
2007-06-25 2:58 ` David Miller
2007-06-25 8:51 ` Patrick McHardy
2007-06-25 11:42 ` David Miller
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=467F82A0.3070801@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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).