lkml.org 
[lkml]   [2007]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 0/6] sys_indirect RFC - sys_indirect introduction
On 6/30/07, Davide Libenzi <davidel@xmailserver.org> wrote:
> This is how all those overloaded syscalls looks like, BTW:
> [...]
> How would you do that with a single shared strcture, w/out adding in all
> signal paths the knowledge of the structure?

You said it yourself: each individual wrapper would look like this.
Generalization really isn't possible, you'll have each wrapper syscall
looking different. This means there is no reason to try coming up
with some overly complicated data structure which would only be useful
if the processing of that data structure could be centralized.
-
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/

\
 
 \ /
  Last update: 2007-07-01 18:29    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site