IMHO add new syscalls it's not a good idea, and the main reason isPortability. The POSIX standards defines a set of syscalls tooperating systems and a lot of other things. Port code (like libc) toa POSIX system is much more easy than port to a non-POSIX, and this iswhy we have softwares running in many platforms (specially in Unixplatforms, like Linux, Solaris, BSD...). Other point is compatibility,if Linux Kernel 2.6.27 add a new syscall to the system, softwares thatuse this syscall will not work on older versions, imagine now othernew syscall in 2.6.27.4 release, same thing... softwares will breakbetween versions, that is bad. Cheers; Renê On Tue, Nov 11, 2008 at 11:49 PM, ??成 <gcchen.org@xxxxxxxxx> wrote:> Hi..> I have two questions:>> 1. Does anyone ever encounter a problem that must be solved by adding> new system calls. If yes, please briefly describe your problem.>> 2. If I add thousands of new system calls (say 2000) in linux kernel> and add these new system calls into sys_call_table, will there be any> stability or performance issues(or other concerns) on this new kernel?> Thanks~~~>> gcchen> --> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in> the body of a message to majordomo@xxxxxxxxxxxxxxx> More majordomo info at http://vger.kernel.org/majordomo-info.html> Please read the FAQ at http://www.linux-learn.org/faqs>?韬{.n?????%??檩??w?{.n???{炳w?'?{ay????j?f＂??????_璁(????"??m???G??⒏??璀?ｘ???O???v??m?? ?)钋?j?⒏?}?
