mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Problem with e100 driver and latency on different packet sizes
Date: Thu, 15 May 2003 15:57:00 -0500	[thread overview]
Message-ID: <3EC3FF1C.7090202@mvista.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E010107D6D0@orsmsx402.jf.intel.com>

Thanks for the response.

I looked at the code, and there doesn't seem to be a way to turn it off
dynamically or with a bootline option.  I have to have the driver
compiled into the kernel (because I'm netbooting with NFS) so I can't
really use a module parameter.

A dynamic field in /proc would be quite nice.

-Corey

Feldman, Scott wrote:

>>I've attached a small program to measure latency of 
>>round-trip time on UDP.  If I send 85-byte packets between 
>>two of my machines, I get 170us round-trip latency.  If I 
>>send 86-byte packets, I get 1329us latency. 
>>This seems quite odd.  If I test on the eepro100 driver, I 
>>get expected linear increase in round-trip time as the packet 
>>size increases, and it never gets close to 1300us.
>>    
>>
>
>This sounds like a side-effect of the "CPU Cycle Saver" feature to
>bundle Rx packets per one interrupt.  See
>Documentation/networking/e100.txt.  I haven't tried your setup, but I
>would guess that you can play around with the BundleSmallFr module
>parameter, or better yet, if you want the lowest latencies, turn off CPU
>Saver (ucode=0).
>
>CPU Saver trades latency for reduced interrupts, resulting in CPU
>savings, hence the name.
>
>Hope this helps.
>
>-scott
>
>
>  
>



  reply	other threads:[~2003-05-15 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 17:12 Feldman, Scott
2003-05-15 20:57 ` Corey Minyard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-15 14:54 Corey Minyard
2003-05-15 17:31 ` Jonathan Brown
2003-05-15 20:11   ` Mark Haverkamp

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=3EC3FF1C.7090202@mvista.com \
    --to=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.feldman@intel.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

Powered by JetHome