From: Eric Dumazet <dada1@cosmosbay.com>
To: akpm@osdl.org
Cc: "David S. Miller" <davem@davemloft.net>,
kiran@scalex86.org, rusty@rustcorp.com.au, dipankar@in.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 0/6] mm: alloc_percpu and bigrefs
Date: Fri, 23 Sep 2005 11:35:37 +0200 [thread overview]
Message-ID: <4333CC69.3000401@cosmosbay.com> (raw)
In-Reply-To: <4333C4E2.9000000@cosmosbay.com>
Andrew Morton a écrit :
> Eric Dumazet <dada1@cosmosbay.com> wrote:
>
>> Please (re)consider this patch since it really reduce CPU load and/or memory
>> bus trafic between CPUS.
>
>
> Did you actually measure this? If so, you should publish the results.
>
>
Hi Andrew
Well yes I did.
Here is part of the mail sent on netdev one month ago :
Hi David
I played and I have very good results with the following patches.
# tc -s -d qdisc show dev eth0 ; sleep 10 ; tc -s -d qdisc show dev eth0
qdisc pfifo_fast 0: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 440173135511 bytes 3211378293 pkt (dropped 240817, overlimits 0
requeues 27028035)
backlog 0b 0p requeues 27028035
qdisc pfifo_fast 0: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 440216655667 bytes 3211730812 pkt (dropped 240904, overlimits 0
requeues 27031668)
backlog 0b 0p requeues 27031668
(So about 360 requeues per second, much better than before (12000 / second))
oprofile results give
0.6257 % qdisc_restart (instead of 2.6452 %)
thread is archived here :
http://marc.theaimsgroup.com/?l=linux-netdev&m=112521684415443&w=2
Thank you
Eric
next prev parent reply other threads:[~2005-09-23 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050923062529.GA4209@localhost.localdomain>
2005-09-23 7:10 ` [patch 0/6] mm: alloc_percpu and bigrefs Andrew Morton
2005-09-23 7:17 ` David S. Miller
2005-09-23 8:11 ` Rusty Russell
2005-09-23 11:36 ` Dipankar Sarma
2005-09-23 18:48 ` Ravikiran G Thirumalai
2005-09-23 9:03 ` Eric Dumazet
2005-09-23 9:35 ` Eric Dumazet [this message]
2005-09-23 18:40 ` Ravikiran G Thirumalai
2005-09-23 18:50 ` David S. Miller
2005-09-23 23:30 ` Ravikiran G Thirumalai
2005-09-23 19:16 ` Christoph Lameter
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=4333CC69.3000401@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.