On Sat, 2008-04-12 at 14:34 +0800, Peter Teoh wrote: > On Sat, Apr 12, 2008 at 2:29 PM, Peter Teoh <htmldeveloper@xxxxxxxxx> wrote: > > > For sure is not advisable on a server but in an embedded devices some > > > I/O locks the system too long if preemption is not configured and > > > adding a real-time layer is too much effort in order to reduce > > > response time just some degrees. > > > > > > > Sorry further to the above, can it be solved by configuring the > different HZ option: > > # CONFIG_NO_HZ is not set > # CONFIG_HZ_100 is not set > CONFIG_HZ_250=y > # CONFIG_HZ_300 is not set > # CONFIG_HZ_1000 is not set > CONFIG_HZ=250 > > Won't that give u a guaranteed (by hardware) regular preemption? > no. without CONFIG_PREEMPT kernel code is not pre-emptable. Userspace code is different - that is always pre-emptable and the HZ options you are looking at help determine the quanta (in either case I believe, assuming config_preempt is enabled) -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
