mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Randy Appleton <rappleto@nmu.edu>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Unneeded Code Found??
Date: Sun, 18 Jan 2004 16:30:19 -0800	[thread overview]
Message-ID: <20040119003019.GF1748@srv-lnx2600.matchmail.com> (raw)
In-Reply-To: <400B2BCF.7090003@nmu.edu>

On Sun, Jan 18, 2004 at 07:58:55PM -0500, Randy Appleton wrote:
> Bill Davidsen wrote:
> >If you never get a hit, it means either (a) your test load actually 
> >doesn't have one, or (b) the code isn't correctly finding them.
> 
> 
> It might be buggy code on my part, but it looks pretty solid to me.   
> I'd be happy to show anyone interested.
> My load ought to find such a merge, if they happen with any freqency at 
> all.  Compiling two kernels
> at the same time and "general running" are my two current loads.  The 
> disk queue gets to over 70
> entries, which is rather high for a personal workstation, and I'm 
> searching tens of thousands to accesses
> in total.
> 
> Does anyone know that this code is actualy useful?  Has anyone ever seen 
> it actually do a merge of consecutive
> data accesses for requests that were not issued themselves consequtively?


What kernel version are you testing against?

  reply	other threads:[~2004-01-19  0:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 23:28 Randy Appleton
2004-01-15 16:02 ` Bill Davidsen
2004-01-19  0:58   ` Randy Appleton
2004-01-19  0:30     ` Mike Fedyk [this message]
2004-01-19  5:54     ` Nick Piggin
2004-01-23 22:23       ` Randy Appleton
2004-01-24  0:00         ` Nick Piggin
2004-01-25 22:36           ` Randy Appleton
2004-01-23 22:10 ` Jens Axboe

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=20040119003019.GF1748@srv-lnx2600.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rappleto@nmu.edu \
    /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

all inboxes | Powered by JetHome®