public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Appleton <rappleto@nmu.edu>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Unneeded Code Found??
Date: Sun, 25 Jan 2004 17:36:57 -0500	[thread overview]
Message-ID: <40144509.4060300@nmu.edu> (raw)
In-Reply-To: <4011B586.1090101@cyberone.com.au>

Nick Piggin wrote:

>
>
> Randy Appleton wrote:
>
>> Nick Piggin wrote: 
>
>
>
>>
>>> Yes it gets used.
>>>
>>> I think its a lot more common with direct io and when you have lots of
>>> processes.
>>
>>
>>
>> I'm not arguing, but how do you know this?  I'm trying to convince 
>> myself that the code is used, and at least on my system
>> a few days of general use, followed by heavy parallel compiles, 
>> doesn't use the code even once.
>>
>> I have not tested direct I/O.  Otherwise it looks unused.
>>
>
> Because I have seen it - I have instrumented it.
>
> Your usage patterns are pretty tame actually. I remember having 100 
> processes
> randomly reading from the same part of the disk was one of my test cases.
> You need direct IO otherwise everything ends up in pagecache.
>
> I haven't seen workloads where it gets used a lot, but that doesn't 
> mean they
> don't exist, and I've never seen the code cause any problems, so there 
> is no
> need to make any trade offs by removing it.
>
O.K.  That's convincing.  Thanks for the time.


  reply	other threads:[~2004-01-25 21:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 23:28 Unneeded Code Found?? Randy Appleton
2004-01-15 16:02 ` Bill Davidsen
2004-01-19  0:58   ` Randy Appleton
2004-01-19  0:30     ` Mike Fedyk
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 [this message]
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=40144509.4060300@nmu.edu \
    --to=rappleto@nmu.edu \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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