Messages in this thread | | | Subject | Re: [lkcd-devel] Re: What's left over. | From | (Eric W. Biederman) | Date | 05 Nov 2002 21:47:58 -0700 |
| |
And the question I was building up to, but forgot to ask.
Given that the kexec code is tied intimately to the kernel implementation.
Given that there is no real advantage in an incremental write model for kexec users (except not needing to allocate a syscall number).
Do you see a better way to structure the kexec interface?
Another file in proc, not carefully placed is just a hair better than an ioctl. Using /proc is not desirable because there are uses of kexec that need a very small kernel, and /proc is a pig, is otherwise useless size bloat.
For some uses including the one that drove me to write it CONFIG_KEXEC and CONFIG_TINY will both be defined.
Eric - 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/
| |