Re: io scheduler silly question perhaps..

From: Nate Diller (nate.diller_at_gmail.com)
Date: 07/29/05

  • Next message: Rajesh Shah: "Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver" 
    Date:	Thu, 28 Jul 2005 17:52:22 -0700
To: Dave Airlie <airlied@linux.ie>

    Try benchmarking Anticipatory or Deadline against Noop, preferably
    with your actual workload. Noop is probably what you want, since
    there is not much use in avoiding large "seeks". It could be though
    that request merging, which the non-noop schedulers all perform, willl
    cause Noop to lose. I haven't tried any I/O scheduler benchmarks with
    flash, but perhaps we need a simple "merge only" scheduler for this
    sort of thing.

    Let me know what the results are.

    NATE

    On 7/28/05, Dave Airlie <airlied@linux.ie> wrote:
    >
    > I have an embedded system which has two read-only flash devices (one a
    > PIO ATA flash disk, and one MDMA capable flash)
    >
    > As I'm doing no writing in this system and most of my reads are sequential
    > (streaming movies or images) would my choice of io scheduler be very
    > important?
    >
    > Regards,
    > Dave.
    >
    > --
    > David Airlie, Software Engineer
    > http://www.skynet.ie/~airlied / airlied at skynet.ie
    > Linux kernel - DRI, VAX / pam_smb / ILUG
    >
    > -
    > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    > the body of a message to majordomo@vger.kernel.org
    > More majordomo info at http://vger.kernel.org/majordomo-info.html
    > Please read the FAQ at http://www.tux.org/lkml/
    >
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Rajesh Shah: "Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver"

    Relevant Pages

    • Re: [PATCH] Consolidate the request merging
      ... moves the backmerging out of the io schedulers and into the elevator ... We save 1.6kb of text and as a bonus get backmerging for noop as ... the deadline scheduler. ... IMO it is a good idea for the noop scheduler to do as much merging as ...
      (Linux-Kernel)
    • Re: [PATCH] Consolidate the request merging
      ... moves the backmerging out of the io schedulers and into the elevator ... We save 1.6kb of text and as a bonus get backmerging for noop as ... the deadline scheduler. ... IMO it is a good idea for the noop scheduler to do as much merging as ...
      (Linux-Kernel)
    • Re: Fall back io scheduler for 2.6.15?
      ... >> I actually thought that elevator= got removed, ... Not an accident at all, actually, because the original patch i ... Since noop is guaranteed to be ... default scheduler is not loaded. ...
      (Linux-Kernel)
    • Re: wrong in_flight diskstat in 2.6.16.1
      ... I see weird output from /sys/block/sd/stat on our AMD64-X2 smp ... scheduler was used, change to noop didn't change anything. ... It is vanilla 2.6.16.1 and here are absolute values in hex and one second differences below: ...
      (Linux-Kernel)
    • Re: io scheduler silly question perhaps..
      ... > Try benchmarking Anticipatory or Deadline against Noop, ... Noop is probably what you want, ... deadline is the appropriate choice, you could still have read starvation ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)