Messages in this thread | | | Date | Sat, 18 Feb 2006 14:45:08 +0530 | From | Dipankar Sarma <> | Subject | Re: [PATCH 1/2] rcu batch tuning |
| |
On Sat, Feb 18, 2006 at 12:45:51AM -0800, Andrew Morton wrote: > Dipankar Sarma <dipankar@in.ibm.com> wrote: > > > > -module_param(maxbatch, int, 0); > > +module_param(blimit, int, 0); > > +module_param(qhimark, int, 0); > > +module_param(qlowmark, int, 0); > > +#ifdef CONFIG_SMP > > +module_param(rsinterval, int, 0); > > +#endif > > It's a bit unusual to add boot-time tunables via module_param, but there's > no law against it. > > But you do get arrested for not adding them to > Documentation/kernel-parameters.txt. That's if you think they're permanent > (I hope they aren't). If they are, they'll probably need a more extensive > description than kernel-parameters.txt entries normally provide.
I hope that we will not need that many tunables eventually. But my theory has been that with widespread use and experiments with the tunables in the event of OOM and latency problems will allow us to figure out what kind of automatic tuning really works.
Regardless, I think there should be documentation. I will send a documentation patch.
Thanks Dipankar
- 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/
| |