>--- linux/include/linux/sysctl.h:1.1.1.3 Sat Oct 31 01:16:09 1998
>+++ linux/include/linux/sysctl.h Sat Oct 31 01:36:44 1998
>@@ -93,7 +93,6 @@
> enum
> {
> /*1*/ VM_SWAPCTL=1, /* struct: Set vm swapping control */
>- VM_SWAPOUT, /* int: Background pageout interval */
> VM_FREEPG, /* struct: Set free page thresholds */
> VM_BDFLUSH, /* struct: Control buffer cache flushing */
> VM_OVERCOMMIT_MEMORY, /* Turn off the virtual memory safety limit */
>
>The problem is that if you do this, you don't just break one single
>sysctl: you break *every single one* in the CTL_VM space, because you
>renumber all of the subsequent sysctl names. You don't have to keep the
>interface totally backwards compatible, but you _do_ have to avoid
>gratuitously breaking the entire interface when you remove a single
>entry.
I know. My point was that _all_ vm sysctl are usually changed via /proc/
interface. And I also thought that many software got broken between 2.0
and 2.1 to allow 2.1 to have a cleaner implementation. So I didn' t care
about that. Probably I was thinking too much aggressive (at least in this
case), so excuse me.
Andrea Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/