From: Dave Hansen <haveblue@us.ibm.com>
To: Mala Anand <manand@us.ibm.com>
Cc: Benjamin LaHaise <bcrl@redhat.com>,
alan@lxorguk.ukuu.org.uk, Bill Hartner <bhartner@us.ibm.com>,
davem@redhat.com, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net,
lse-tech-admin@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: (RFC): SKB Initialization
Date: Thu, 22 Aug 2002 12:02:27 -0700 [thread overview]
Message-ID: <3D653543.6000403@us.ibm.com> (raw)
In-Reply-To: OF126E7130.D54285DD-ON87256C1C.0077A747@boulder.ibm.com
Mala Anand wrote:
> The third scope would be measuring this patch in a workload environment.
> We measured it in a web serving workload and found that we get 0.7%
> improvement.
First of all, the patch doesn't apply at all against the current
bitkeeper tree. I can post the exact one I used if you like.
I tried this under our Specweb99 setup. Here's a snippet of
readprofile with, then without the patch:
8788 __kfree_skb
8970 mod_timer
9095 file_read_actor
10778 alloc_skb
10905 skb_clone
11368 e1000_clean_tx_irq
13595 e1000_intr
18367 csum_partial_copy_generic
27848 e1000_xmit_frame
225838 poll_idle
623160 total 0.4107
alloc:free ratio: 1.226
(__kfree_skb+alloc_skb)/total = 3.14%
4535 alloc_skb
4559 do_tcp_sendpages
4596 e1000_clean_rx_irq
4847 dev_queue_xmit
5020 tcp_clean_rtx_queue
5155 batch_entropy_store
5165 kmalloc
5309 tcp_transmit_skb
6060 do_schedule
6138 qdisc_restart
6235 tcp_v4_rcv
6393 kfree
6787 do_gettimeofday
7089 __d_lookup
7810 ip_queue_xmit
8303 skb_clone
8858 file_read_actor
8885 mod_timer
9375 .text.lock.namei
10267 .text.lock.dec_and_lock
10936 e1000_clean_tx_irq
13001 __kfree_skb
13322 skb_release_data
13562 e1000_intr
18099 csum_partial_copy_generic
27447 e1000_xmit_frame
225023 poll_idle
628695 total 0.4143
alloc:free ratio: 0.348
(__kfree_skb+alloc_skb)/total = 2.79%
You can see the entire readprofile here:
http://www.sr71.net/~specweb99/run-specweb-100sec-2400-2.5.31-bk+4-kmap-08-22-2002-11.20.17/
http://www.sr71.net/~specweb99/run-specweb-100sec-2400-2.5.31-bk+4-kmap-mala-08-22-2002-11.44.25/
No, I don't know why I have so much idle time.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-08-22 18:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 17:22 [Lse-tech] Re: (RFC): SKB Initialization Mala Anand
2002-08-22 18:32 ` Benjamin LaHaise
2002-08-22 19:02 ` Dave Hansen [this message]
2002-08-22 20:58 ` [Ibm-specweb99] " Nivedita Singhvi
2002-08-22 22:05 ` William Lee Irwin III
2002-08-23 19:09 ` Bill Hartner
-- strict thread matches above, loose matches on Subject: below --
2002-08-23 14:44 Mala Anand
2002-08-23 16:39 ` Dave Hansen
2002-08-23 20:12 ` Bill Hartner
2002-08-23 20:30 ` Dave Hansen
2002-08-23 23:36 ` Troy Wilson
2002-08-23 20:51 ` Rick Lindsley
2002-08-23 22:41 ` David S. Miller
2002-08-23 23:14 Mala Anand
2002-08-23 23:38 Mala Anand
2002-08-23 23:55 ` David S. Miller
2002-08-25 16:17 jamal
2002-08-25 22:51 ` David S. Miller
2002-08-25 20:12 Mala Anand
2002-08-26 1:02 ` jamal
2002-08-26 13:04 Mala Anand
2002-08-26 19:28 ` Robert Olsson
2002-08-27 10:17 ` jamal
2002-08-27 2:53 Mala Anand
2002-08-27 13:18 Mala Anand
2002-08-27 15:49 ` jamal
2002-09-03 3:47 Mala Anand
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=3D653543.6000403@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=bhartner@us.ibm.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech-admin@lists.sourceforge.net \
--cc=lse-tech@lists.sourceforge.net \
--cc=manand@us.ibm.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