Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: oprofiling is much saner looking now with rc6-smoketest
Date: Tue, 30 Aug 2011 17:32:00 -0700	[thread overview]
Message-ID: <CAA93jw6Mbp2jBV6ZXngh2R9CmFWMR1L-9PqzdFGySQ6Y3MdPPg@mail.gmail.com> (raw)

I get about 190Mbit/sec from netperf now, on GigE, with oprofiling
enabled, driver buffers of 4, txqueue of 8, cerowrt default iptables
rules,
AND web10g patched into kernel 3.0.3.

This is much saner than rc3, and judging from the csum_partial and
copy_user being roughly equal, there isn't much left to be gained...

Nice work.

(Without oprofiling, and without web10g and with tcp cubic I can get
past 250Mbit)


CPU: MIPS 24K, speed 0 MHz (estimated)
Counted INSTRUCTIONS events (Instructions completed) with a unit mask
of 0x00 (No unit mask) count 100000
samples  %        app name                 symbol name
-------------------------------------------------------------------------------
17277    13.8798  vmlinux                  csum_partial
  17277    100.000  vmlinux                  csum_partial [self]
-------------------------------------------------------------------------------
16607    13.3415  vmlinux                  __copy_user
  16607    100.000  vmlinux                  __copy_user [self]
-------------------------------------------------------------------------------
11913     9.5705  ip_tables                /ip_tables
  11913    100.000  ip_tables                /ip_tables [self]
-------------------------------------------------------------------------------
8949      7.1893  nf_conntrack             /nf_conntrack
  8949     100.000  nf_conntrack             /nf_conntrack [self]


In this case I was going from laptop - gige - through another
rc6-smoketest router - to_this_box's internal lan port.

It bugs me that iptables and conntrack eat so much cpu for what
is an internal-only connection, e.g. one that
doesn't need conntracking.

That said, I understand that people like their statistics, and me,
I'm trying to make split-tcp work better, ultimately, one day....

I'm going to rerun this without the fw rules next.

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

             reply	other threads:[~2011-08-31  0:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31  0:32 Dave Taht [this message]
2011-08-31  1:01 ` Rick Jones
2011-08-31  1:10   ` Simon Barber
2011-08-31  1:20     ` Simon Barber
2011-08-31  1:45   ` Dave Taht
2011-08-31  1:58     ` Dave Taht
2011-08-31  3:28       ` Dave Taht
2011-08-31 16:19         ` Rick Jones
2011-08-31 15:55     ` Rick Jones
2011-08-31  1:41 ` Dave Taht

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=CAA93jw6Mbp2jBV6ZXngh2R9CmFWMR1L-9PqzdFGySQ6Y3MdPPg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    /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