From: "Serge Kuznetsov" <serge@wcom.ca>
To: "Anton Blanchard" <anton@samba.org>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.50 + e100 benchmarking
Date: Mon, 9 Dec 2002 13:08:56 -0500 [thread overview]
Message-ID: <044101c29fae$0a7bb300$9c094d8e@wcom.ca> (raw)
In-Reply-To: 20021208124444.GA18751@krispykreme
> e100_intr was the worst function in a profile. PCI reads are very costly
I profiled this part and I found what the main issue is the e100_alloc_skbs.
It takes from 10000 to ~19000 processor's tacts.
At the same time eepro100's speedo_iterrupt is pretty fast.
All the Best!
Serge.
prev parent reply other threads:[~2002-12-09 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 12:44 2.5.50 + e100 benchmarking Anton Blanchard
2002-12-08 20:08 ` Andrew Morton
2002-12-09 13:59 ` Anton Blanchard
2002-12-09 18:08 ` Serge Kuznetsov [this message]
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='044101c29fae$0a7bb300$9c094d8e@wcom.ca' \
--to=serge@wcom.ca \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
/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