[lkml]   [2007]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCHv3 0/4] sys_indirect system call
    Hash: SHA1

    H. Peter Anvin wrote:
    > What bothers me about the sys_indirect approach is that it will get
    > increasingly expensive as time goes on, and in doing so it does a
    > user-space memory reference, which are extra expensive. The extra table
    > can be colocated with the main table (a structure, in effect) so they'll
    > share the same cache line.

    You assume that using sys_indirect will be the norm. It won't. We
    mustn't design system calls deliberately wrong so that they require the

    Beside, if the number of syscalls which has to be handled this way grows
    we can use something more efficient for large numbers of test than a
    switch statement. It could even be a word next to the system call table.

    But I still don't see that the magic encoding is a valid solution, it
    doesn't address the limited parameter number. Plus, using sys_indirect
    could in future be used to transport entire parameters (like a sigset_t)
    along with other information, thereby saving individual copy operations.

    I think the sys_indirect approach is the way forward. I'll submit a
    last version of the patch in a bit.

    - --
    ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
    Version: GnuPG v1.4.7 (GNU/Linux)

    -----END PGP SIGNATURE-----
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-11-20 04:31    [W:0.022 / U:2.444 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site