Re: [PATCH] improving JOB kernel/user interface

[Chris Wright]

* John Hesterberg (jh@xxxxxxx) wrote:
> The current job /proc ioctl interface is really a fake-syscall interface.
> We only did that so that our product didn't have to lock into a syscall
> number that would eventually be used by something else.
> 
> The easiest thing for us would probably be to turn it back into a system
> call, if that would be acceptable for inclusion into the kernel.  We're
> open to other job interfaces, such as a real /proc character interface,
> or a new virtual filesystem, or a device driver using ioctls.

But that system call would still be a single mutliplexor for many calls, right?
Not ideal.  Have you tried to map to an fs?  It's nice and contained, and may be a
simple mapping.  Question comes with CKRM, and if they'll have similar needs.  If
that's the case, first class syscalls (no multiplexor) may be way to go.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net
-
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/