Re: elevator algorithm bug in ll_rw_blk.c

Alain Knaff (alain@linux.lu)
Sun, 22 Nov 1998 12:18:30 +0100


In linux, you wrote:
>
>> yes, but doing this when mkfs runs might be feasable
>> or perhaps why not tackle a subset of the problem and just optimise swap partitions
>mkfs may run at heavy-load time. The only safe time to do timing-sensitive
>probing is at device driver initialization time, and that is
>inconvenient.

Wouldn't it be possible to do it once at disk _installation_ time?

That is:
1) buy the disk,
2) put it into the box,
3) run the detection program (which may run several hours...). For
more precision, run the detection program out of a small Linux system
booted from a _different_ disk, or from floppy.
4) when done, the detection program dumps its findings to a file.
5) later on, the disk driver just reads the data stored in that file
at boot, without having to run the optimization program again.

And for those who don't want to spend several hours running that disk
optimization utilitiy, they could always go to a website where we
would centralize that kind of info (assuming same disk type = same
characteristics).

> And it may still fail due to caching and buffering
>in the disk itself.

>The task isn't easier for swap partitions, although a simple
>optimization can be done by preferring to use the fastest side
>of the partition first. This can be determined by a simple program.
>
>Helge Hafting
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.rutgers.edu
>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.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/