Re: another IDE cleanup: kill duplicated code

From: Vojtech Pavlik (vojtech@suse.cz)
Date: Tue Feb 12 2002 - 08:43:00 EST

Next message: David S. Miller: "Re: thread_info implementation"
Previous message: Davidovac Zoran: "Re: secure erasure of files?"
In reply to: Martin Dalecki: "Re: another IDE cleanup: kill duplicated code"
Next in thread: Martin Dalecki: "Re: another IDE cleanup: kill duplicated code"
Reply: Martin Dalecki: "Re: another IDE cleanup: kill duplicated code"
Reply: Jens Axboe: "Re: another IDE cleanup: kill duplicated code"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, Feb 12, 2002 at 02:17:48PM +0100, Martin Dalecki wrote:

> So the conclusions is that not just the read_ahead array is bogous now.
> The max_readahead array can be killed entierly from the kernel as well ;-).
>
> The answer is: I'm now confident that you can just remove all the
> max_readahead initialization from the ide code.

Since I've come to the same conclusion, here is the patch. It removes
read_ahead, max_readahead, BLKRAGET, BLKRASET, BLKFRAGET and BLKFRASET
completely.

Comments, Jens?

-- Vojtech Pavlik SuSE Labs

text/plain attachment: readahead-clean-2.diff

- 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: David S. Miller: "Re: thread_info implementation"
Previous message: Davidovac Zoran: "Re: secure erasure of files?"
In reply to: Martin Dalecki: "Re: another IDE cleanup: kill duplicated code"
Next in thread: Martin Dalecki: "Re: another IDE cleanup: kill duplicated code"
Reply: Martin Dalecki: "Re: another IDE cleanup: kill duplicated code"
Reply: Jens Axboe: "Re: another IDE cleanup: kill duplicated code"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:00:49 EST