On Tue, 12 Jul 2005, Eric Lowe wrote: > .. and the goal should really be zero tunables (the system should be as > self tuning as possible -- you don't set your spark timing and fuel mixture > from the dash of your car ever morning do you?). A good number of the > tunables that remain are well known are knobs into really old code that > should probably be rewritten, or is already on the chopping block.
Keep in mind that there's tunables like you seem to be thinking about that presumably can be eliminated / minimized (such as SysV IPC). However, there's also on-off knobs that are always going to be needed -- ip_forwarding, for example, and ip_strict_dst_multihoming and all the other networking knobs. Whether you expose that through sysctl (Linux) or through a mixture of /etc/system and ndd (Solaris) it needs to be there. Those sorts of networking knobs seem to be most of what I see adjusted on customers' Linux deployments (Linux does have lots of memory knobs and similar tunables, but they aren't used that much in practice that I've seen; certainly no more so than they are on the Solaris boxes I see), and at least Linux has the advantage that it provides a standard interface for making those sorts of networking configurations permanent (sysctl.conf). Solaris OTOH splits the stuff people care about changing between /etc/system and the transient ndd.... later, chris _______________________________________________ opensolaris-code mailing list [email protected] https://opensolaris.org:444/mailman/listinfo/opensolaris-code
