From: Benjamin LaHaise <bcrl@redhat.com>
To: Mala Anand <manand@us.ibm.com>
Cc: alan@lxorguk.ukuu.org.uk, davem@redhat.com,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
Bill Hartner <bhartner@us.ibm.com>
Subject: Re: (RFC): SKB Initialization
Date: Wed, 21 Aug 2002 13:10:48 -0400 [thread overview]
Message-ID: <20020821131048.B8001@redhat.com> (raw)
In-Reply-To: <OF9AEE9308.79FD144F-ON87256C1C.004716B7@boulder.ibm.com>; from manand@us.ibm.com on Wed, Aug 21, 2002 at 11:59:44AM -0500
On Wed, Aug 21, 2002 at 11:59:44AM -0500, Mala Anand wrote:
> The patch reduces the numer of cylces by 25%
The data you are reporting is flawed: where are the average cycle
times spent in __kfree_skb with the patch? Without that information,
there is no basis for conclusion as the total time spent in these
two routines is unknown. At worst, I'd have to assume this lack of
scientific method is an attempt to hide some aspect of the resulting
behaviour, but I hope that isn't the case.
-ben
> Baseline on Linux 2.5.25 kernel:
> -------------------------------
>
> CPU 0 CPU 1
> ------ ------
> Avg cycles in alloc_skb: 64.05 203.39
> Avg cycles in __kfree_skb: 127.54 228.95
> ------ -------
> Total Avg Cycles 191.59 432.34
> ------ -------
>
> # of times alloc_skb called: 235,478 2,060,422
> # of times __kfree_skb called: 2,063,276 232,359
>
>
> Linux 2.5.25+Skbinit Patch:
> --------------------------
> CPU 0 CPU 1
> ----- -----
> Avg cycles in alloc skb: 237.21 230.91
>
> # of times alloc_skb called: 1,226,594 1,213,327
next prev parent reply other threads:[~2002-08-21 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 16:59 (RFC): SKB Initialization Mala Anand
2002-08-21 17:10 ` Benjamin LaHaise [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-21 18:07 Mala Anand
2002-08-21 18:16 ` Benjamin LaHaise
2002-08-21 18:42 Nivedita Singhvi
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=20020821131048.B8001@redhat.com \
--to=bcrl@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bhartner@us.ibm.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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