Subject: Re: bufq and sysctl question
To: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
From: Julio M. Merino Vidal <jmmv84@gmail.com>
List: tech-kern
Date: 01/22/2006 21:52:53
El 22/01/2006, a las 21:28, YAMAMOTO Takashi escribi=F3:

>> [juan@Nocturno][~]> sudo sysctl -w kern.bufq.readprio.read_burst=3D512
>> kern.bufq.readprio.read_burst: 128 -> 512
>> [juan@Nocturno][~]> sysctl kern.bufq.readprio
>> kern.bufq.readprio.read_burst =3D 512
>> kern.bufq.readprio.write_req =3D 64
>> [juan@Nocturno][~]>
>>
>> yamt, is it ready to commit?
>
> i don't think having these sysctls is a good idea.
> if we should have these knobs, they should be per-bufq.
> and, IMO, they should be a part of DIOCGSTRATEGY/DIOCSSTRATEGY.
> dks_param/dks_paramlen in struct disk_strategy was intended for
> this kind of feature.
> (ie. pass a string like "read_burst=3D512, write_req=3D64".
> i think having an option string parser in kernel is not so wasteful,
> as far as it can be used for others like mount(2).)

FWIW, i was thinking to write one (a string option parser) for the
multiboot support code I was working on.  (Just to mention another
place where it can be useful.)

--=20
Julio M. Merino Vidal <jmmv84@gmail.com>
The Julipedia - http://julipedia.blogspot.com/