[lkml]   [2009]   [Apr]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectIdea: Feature information / extensions dispatcher syscall.

    System calls is a very convenient way to talk to modules. But when some modules
    used locally (e.g. in one organization only) it will be to impractical
    to reserve system
    call number in linux kernel source for that feature forever. Usually
    first free syscall
    number is used. But when new system call is introduced in official kernel,
    one need to rewrite all modules and libraries, since first free
    syscall number is increased.

    I suggest to reserve one system call to provide information about
    other system calls.
    This can help to build system call independent programs.

    That informational / dispatcher system call can take some identifier
    as argument (e.g. GUID)
    and return some information about asked extension (e.g. syscall number
    for that extension).

    So libraries that use some additional functionality upon first call of
    extension function
    will ask kernel (via informational syscall), what is the number of
    feature's syscall, and will
    use it later directly.

    Also can be useful to reserve some system call number (e.g. 8) for
    such extensions,
    so extension modules can use first unused number of this set.

    This allow to use system calls in any extension modules without need to reserve
    syscall number in kernel source and allow binaries to run correctly on
    any kernel
    (where that extension feature can have another syscall number).

    What do you think?

     \ /
      Last update: 2009-04-22 16:15    [W:0.019 / U:14.452 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site