From: Scott Feldman <sfeldma@pobox.com>
To: Malli Chilakala <mallikarjuna.chilakala@intel.com>
Cc: netdev <netdev@oss.sgi.com>, "jgarzik@pobox.com" <jgarzik@pobox.com>
Subject: Re: [PATCH net-drivers-2.6 5/6] e100: Performance optimizations to e100 Tx Path
Date: Thu, 21 Apr 2005 09:55:00 -0700 [thread overview]
Message-ID: <7e4e52dab6e50d8fc38c76651cac0f07@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504190534410.11186@anoushka.jf.intel.com>
On Apr 19, 2005, at 10:50 PM, Malli Chilakala wrote:
> Performance optimizations to e100 Tx Path
So what is the net performance improvement with these changes?
> - nic->tx_command = cpu_to_le16(cb_tx | cb_i | cb_tx_sf |
> - ((nic->mac >= mac_82558_D101_A4) ? cb_cid : 0));
> + /* no interrupt for every tx completion, delay = 256us if not 557*/
> + nic->tx_command = cpu_to_le16(cb_tx | cb_tx_sf |
> + ((nic->mac >= mac_82558_D101_A4) ? cb_cid : cb_i));
Where is this 256us delay coming from?
> /* Template for a freshly allocated RFD */
> nic->blank_rfd.command = cpu_to_le16(cb_el);
> @@ -1289,12 +1294,15 @@ static inline void e100_xmit_prepare(str
> struct sk_buff *skb)
> {
> cb->command = nic->tx_command;
> + /* interrupt every 16 packets regardless of delay */
> + if((nic->cbs_avail & ~15) == nic->cbs_avail) cb->command |= cb_i;
You messed up Big Endian.
So you send out 15 packets with no i-bit set. Then what? No interrupt
means no NAPI means no cleanup of those 15 packet skbs.
-scott
P.S. I only saw this one patch for e100 but the subject line indicates
there are 6.
next prev parent reply other threads:[~2005-04-21 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 5:50 [PATCH net-drivers-2.6 5/6] e100: Performance optimizations to e100 Tx Path Malli Chilakala
2005-04-21 3:05 ` Randy.Dunlap
2005-04-21 16:51 ` Ganesh Venkatesan
2005-04-21 17:10 ` Randy.Dunlap
2005-04-21 16:55 ` Scott Feldman [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 18:59 Brandeburg, Jesse
2005-04-21 19:17 ` Scott Feldman
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=7e4e52dab6e50d8fc38c76651cac0f07@pobox.com \
--to=sfeldma@pobox.com \
--cc=jgarzik@pobox.com \
--cc=mallikarjuna.chilakala@intel.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).