From: Eric Dumazet <eric.dumazet@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] tcp: avoid expensive pskb_expand_head() calls
Date: Wed, 18 Apr 2012 19:40:48 +0200 [thread overview]
Message-ID: <1334770848.2472.314.camel@edumazet-glaptop> (raw)
In-Reply-To: <4F8EFA24.8020909@hp.com>
On Wed, 2012-04-18 at 10:30 -0700, Rick Jones wrote:
> I was thinking more about the race if any between the ACK for the last
> byte of the 64 KB skb and the transmit completion processing freeing it
> in the driver. But that may be moot.
>
No race, its done with atomic operations.
> >
> > # perf stat -r 5 -d -d -o RES.before taskset 1 netperf -H 192.168.99.1 -l 20
>
> I'm still learning about perf, and the manpage I have for it does not
> discuss the -d option but is that doing system wide, or only in the
> context of the netperf process?
In fact I used -a option and forgot to copy it in the mail I sent
perf stat -h
usage: perf stat [<options>] [<command>]
-e, --event <event> event selector. use 'perf list' to list available events
--filter <filter>
event filter
-i, --no-inherit child tasks do not inherit counters
-p, --pid <pid> stat events on existing process id
-t, --tid <tid> stat events on existing thread id
-a, --all-cpus system-wide collection from all CPUs
-g, --group put the counters into a counter group
-c, --scale scale/normalize counters
-v, --verbose be more verbose (show counter open errors, etc)
-r, --repeat <n> repeat command and print average + stddev (max: 100)
-n, --null null run - dont start any counters
-d, --detailed detailed run - start a lot of events
-S, --sync call sync() before starting a run
-B, --big-num print large numbers with thousands' separators
-C, --cpu <cpu> list of cpus to monitor in system-wide
-A, --no-aggr disable CPU count aggregation
-x, --field-separator <separator>
print counts with custom separator
-G, --cgroup <name> monitor event in cgroup name only
-o, --output <file> output file name
--append append to the output file
--log-fd <n> log output to fd, instead of stderr
next prev parent reply other threads:[~2012-04-18 17:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 9:06 [BUG] ixgbe: something wrong with queue selection ? Eric Dumazet
2012-04-17 9:16 ` Jeff Kirsher
2012-04-17 16:01 ` Alexander Duyck
2012-04-17 16:38 ` John Fastabend
2012-04-17 17:07 ` Ben Hutchings
2012-04-17 16:46 ` Eric Dumazet
2012-04-17 21:38 ` TSO not 10G friendly if peer is close enough Eric Dumazet
2012-04-17 21:47 ` David Miller
2012-04-18 3:00 ` Eric Dumazet
2012-04-18 15:49 ` [PATCH net-next] tcp: avoid expensive pskb_expand_head() calls Eric Dumazet
[not found] ` <4F8EF317.10504@hp.com>
2012-04-18 17:16 ` Eric Dumazet
2012-04-18 17:30 ` Rick Jones
2012-04-18 17:40 ` Eric Dumazet [this message]
2012-04-18 18:40 ` Neal Cardwell
2012-04-18 19:18 ` Eric Dumazet
2012-04-18 19:51 ` [PATCH v2 " Eric Dumazet
2012-04-19 11:10 ` Ilpo Järvinen
2012-04-19 11:30 ` Eric Dumazet
2012-04-19 11:40 ` Eric Dumazet
2012-04-19 11:57 ` Ilpo Järvinen
2012-04-19 12:44 ` Eric Dumazet
2012-04-20 12:27 ` Ilpo Järvinen
2012-04-19 13:18 ` Eric Dumazet
2012-04-19 13:52 ` Eric Dumazet
2012-04-19 14:10 ` Eric Dumazet
2012-04-19 17:20 ` Rick Jones
2012-04-19 17:25 ` Eric Dumazet
2012-04-19 17:48 ` Rick Jones
2012-04-19 18:00 ` Eric Dumazet
2012-04-19 18:05 ` Rick Jones
2012-04-18 19:41 ` [PATCH " Vijay Subramanian
2012-04-18 19:49 ` Eric Dumazet
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=1334770848.2472.314.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
/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