Re: [PATCHv4 0/6] sys_indirect system call

From: Ulrich Drepper
Date: Tue Nov 20 2007 - 11:12:28 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric Dumazet wrote:
> I am wondering if some parts are missing from your ChangeLog
>
> You apparently added in v3 a new 'flags' parameter to indirect syscall
> but no trace of this change in Changelog, and why it was added. This
> seems to imply a future multiplexor.

This was mentioned in one of my mails. I added the parameter to
accommodate Linus's and Zack's idea to use the functionality for syslets
as well. Not really a multiplexer, it is meant to be a "execute
synchronously or asynchronously" flag. In the latter case an additional
parameter might be needed to indicate the notification mechanism.


> And no change in the test program reflecting this 'flags' new param, so
> it fails.

Yep, sorry, I didn't update the text by including the most recent test
program. I'll do that for the next version.

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

iD8DBQFHQwca2ijCOnn/RHQRAgQJAKDH+N3+FSJ0kD5VbzbAFN4918wREwCePHbc
nSY/t9x1FuYstYDaaT6Kut0=
=c95e
-----END PGP SIGNATURE-----
-
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/