On Sat, 19 Aug 2000, Cesar Eduardo Barros wrote:
> include/linux/elevator.h says max_bomb_segments defaults to zero.
>
> drivers/block/elevator.c (blkelvset_ioctl) says it can't be zero.
Heh, the new elevator is like 3 months (?) old...
And it's _already_ suffering from bitrot?!
> One of them must be wrong.
They're probably _both_ wrong. With all the threads on
linux-kernel about people getting poor performance with
the magic numbers in the elevator set wrong, I'm getting
the impression that that code really needs to be capable
of auto-tuning itself at run time.
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo _at_ vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: bogosity in blkelvset_ioctlAndrea Arcangeli <andrea _at_ suse.de>
- bogosity in blkelvset_ioctlCesar Eduardo Barros <cesarb _at_ nitnet.com.br>
- Prev by Date: bogosity in blkelvset_ioctl
- Next by Date: [PATCH] Enabling access to the full nvram memory
- Prev by thread: bogosity in blkelvset_ioctl
- Next by thread: Re: bogosity in blkelvset_ioctl
- Indexes:[Main][Thread]