Re: [PATCH 0/4] sys_indirect system call

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Zach Brown <zach.brown@...>
Cc: Ulrich Drepper <drepper@...>, <linux-kernel@...>, <akpm@...>, Ingo Molnar <mingo@...>
Date: Thursday, November 15, 2007 - 6:33 pm

On Thu, 15 Nov 2007, Zach Brown wrote:

Yes, I mentioned this to Ulrich as one of the things that would make 
sense.

Uli doesn't care that much about async syscalls, but I think that from a 
kernel standpoint, we'd want to use this same indirect call for async 
scheduling, rather than have two separate interfaces (because async 
scheduling will want to have all the same flags intefaces for 
open/socket/etc *too* and a doubly-indirect setup would be insanity!)

And it definitely fits the bill as a really simple syslet model for the 
trivial case of doing just single system calls asynchronously.

		Linus
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 0/4] sys_indirect system call, Ulrich Drepper, (Thu Nov 15, 12:41 pm)
Re: [PATCH 0/4] sys_indirect system call, Zach Brown, (Thu Nov 15, 6:19 pm)
Re: [PATCH 0/4] sys_indirect system call, Linus Torvalds, (Thu Nov 15, 6:33 pm)
Re: [PATCH 0/4] sys_indirect system call, Ulrich Drepper, (Sat Nov 17, 5:14 am)
Re: [PATCH 0/4] sys_indirect system call, Ulrich Drepper, (Thu Nov 15, 7:30 pm)
Re: [PATCH 0/4] sys_indirect system call, Zach Brown, (Thu Nov 15, 7:40 pm)