The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "Christopher Friesen" <cfriesen@nortelnetworks.com>
Cc: Davide Libenzi <davidel@xmailserver.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	arr@watson.org, skraw@ithnet.com, lkml@lpbproductions.com
Subject: Re: question on incoming packets and scheduler
Date: Wed, 15 Oct 2003 16:53:44 -0400	[thread overview]
Message-ID: <3F8DB3D8.3050406@nortelnetworks.com> (raw)
In-Reply-To: 3F8DAA6B.7060609@nortelnetworks.com

Friesen, Christopher [CAR:7Q28:EXCH] wrote:


> With 2.4.[18-20], the overall average goes up when the number of packets 
> goes up.  For 2.6.0-test6, it stays constant.

Okay, its official.  My brain isn't working.

The different kernels were tested on two different machines.  The one 
running 2.4 is *just* enough slower that the packets start to pile up 
and end up waiting in the socket buffer.  By slowing down the packet 
sending I get results that are invariant with the number of packets.

Sorry for the false alarm guys....

Chris




-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


      parent reply	other threads:[~2003-10-15 20:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15  1:39 question on incoming packets and scheduler Chris Friesen
2003-10-15  3:42 ` Chris Friesen
2003-10-15 17:39 ` Davide Libenzi
2003-10-15 18:17   ` Chris Friesen
2003-10-15 18:35     ` Davide Libenzi
2003-10-15 20:13       ` Chris Friesen
2003-10-15 20:27         ` Andrew R. Reiter
2003-10-15 20:53         ` Chris Friesen [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=3F8DB3D8.3050406@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=arr@watson.org \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@lpbproductions.com \
    --cc=skraw@ithnet.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