Re: Request: I/O request recording

From: Davide Libenzi (davidel_at_xmailserver.org)
Date: 01/25/04

  • Next message: Jeff Garzik: "Re: [PATCH] [2.4] forcedeth network driver"
    Date:	Sat, 24 Jan 2004 15:53:44 -0800 (PST)
    To: Andrew Morton <akpm@osdl.org>
    
    

    On Sat, 24 Jan 2004, Andrew Morton wrote:

    > Felix von Leitner <felix-kernel@fefe.de> wrote:
    > >
    > > I would like to have a user space program that I could run while I cold
    > > start KDE. The program would then record which I/O pages were read in
    > > which order. The output of that program could then be used to pre-cache
    > > all those pages, but in an order that reduces disk head movement.
    > > Demand Loading unfortunately produces lots of random page I/O scattered
    > > all over the disk.
    >
    > I wrote a similar thing in September of 2001. What you do is:
    >
    > - Reboot the system, wait until everything is steady-state (eg: X has
    > started, applications are loaded).
    >
    > - Load a kernel module which dumps the current contents of the pagecache
    > (filename/offset-into-file) into a file.
    >
    > (The kernel module writes to modprobe's stdout, so you just do
    >
    > modprobe fboot-dump > /tmp/fboot-dump.out
    >
    > I'm very proud of this.)
    >
    > - Post-process the resulting output into a database which is used on the
    > next reboot.
    >
    > - reboot
    >
    > - This time a userspace application cuts in real early and reads the
    > database and preloads all the pagecache using "optimal" I/O patterns so
    > that everything which you will need in the subsequent boot is already in
    > memory.
    >
    >
    > So it's all an attempt to optimise the boot-time I/O patterns. It was
    > pretty much a waste of time, gaining only 10% or so, from memory. You
    > could get just as much or more speedup from simply launching all the
    > initscripts in parallel, although this did tend to break stuff.
    >
    > Anyway, the code's ancient but might provide some ideas:
    >
    > http://www.zip.com.au/~akpm/linux/fboot.tar.gz

    Warning. I don't know if they do have a patent for this, but MS does this
    starting from XP (look inside %WINDIR%\PreFetch). It is both boot and app
    based.

    - Davide

    -
    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: Jeff Garzik: "Re: [PATCH] [2.4] forcedeth network driver"

    Relevant Pages

    • Re: Request: I/O request recording
      ... > Demand Loading unfortunately produces lots of random page I/O scattered ... - Reboot the system, wait until everything is steady-state (eg: ... pretty much a waste of time, gaining only 10% or so, from memory. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Something corrupts raid5 disks slightly during reboot
      ... corruption after reboot and perfect work inbetween. ... Any theories on how faulty memory could actually cause something like this? ... A bad spot in memory on an area where the bios code is cached, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Possible dcache BUG
      ... > I had to reboot late last night, out of memory and things (like ... > mozilla were dying, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Random reboots with M2N-E (even worse now)
      ... error that happens during the reboot, ... I've known memory beeps to be 3 short ones, but this is on the Award ... When I couldn't find the 2.1V setting in the BIOS to adjust the memory ... you should get the same beep code. ...
      (alt.comp.periphs.mainboard.asus)
    • Re: Weird XP Start-Up Problem - Please help!
      ... but a while ago we built a number of PCs with gigabyte motherboards and I can't remember what memory but after XP was installed the following day a number of these PCs didn't boot, they blue screened but after that each PC started perfectly ran every test we could think of and nothing. ... Seems crazy and even telling the customer to hold the power button for a second longer when switching on they looked at me crazy but it worked.. ... CHECKING FILE SYSTEM ON D: ... reboot I get the standard "Sorry for the inconvenience" screen to ...
      (microsoft.public.windowsxp.general)