Re: [PATCH 0/22] Introducing asm/syscalls.h
From: Jaswinder Singh
Date: Mon Jul 21 2008 - 03:01:24 EST
On Mon, 2008-07-21 at 00:16 -0600, Matthew Wilcox wrote:
> sys_fork() does seem to be the worst case scenario. I suspect there's
> similar ones (clone?). I still think it's worth adding them all to
I tried my best to make things simpler. I also tried this in :-
[PATCH 17/22] sh: Introducing asm/syscalls.h
[PATCH 21/22] x86: Introducing asm/syscalls.h
For same architecture it looks complex for 32 and 64 bit.
You can Imagine how linux/syscalls.h will look if we add all
architectures in it.
And you can imagine what will be size of linux/syscalls.h. As more than
60% of arch dependent syscalls have totally different prototypes.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/