All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@lexus.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Testing the effects of the low latency patch
Date: Thu, 24 Jan 2002 17:37:01 -0800	[thread overview]
Message-ID: <3C50B6BD.8080307@lexus.com> (raw)
In-Reply-To: <3C50AC22.7090203@lexus.com> <3C50AEE1.2300BB05@zip.com.au> <3C50B185.40006@lexus.com> <3C50B37C.9EACC94B@zip.com.au>

It was during gameplay, no dbench running, which
as it turns out is a workload of interest for me -

Joe

Andrew Morton wrote:

>J Sloan wrote:
>
>>>>2.4.18-pre6+tux+nfs-fixes
>>>>-------------
>>>>...
>>>>7.6 1
>>>>7.8 1
>>>>21.1 1
>>>>
>>>This is the stock kernel.  In twenty minutes you suffered
>>>precisely *one* scheduling overrun which is perceptible
>>>by a human.  The rest are much shorter than your monitor's
>>>refresh interval.  Interesting, yes?
>>>
>>Yes, the stock kernel is much improved from
>>say 6 months ago. I will take a look at the
>>kernel that shipped with my distro just for
>>giggles as well...
>>
>
>Was you histogram generated during a game session, or during
>dbench?  write()-intensive workloads are the main common
>offender.
>
>-
>



  reply	other threads:[~2002-01-25  1:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  0:51 Testing the effects of the low latency patch J Sloan
2002-01-25  1:03 ` Andrew Morton
2002-01-25  1:14   ` J Sloan
2002-01-25  1:23     ` Andrew Morton
2002-01-25  1:37       ` J Sloan [this message]
2002-01-25  1:19 ` J Sloan
2002-01-25  1:39   ` Mark Hahn
2002-01-25  2:26     ` J Sloan

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=3C50B6BD.8080307@lexus.com \
    --to=jjs@lexus.com \
    --cc=akpm@zip.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.