On Mon, 5 Feb 2007, Davide Libenzi wrote: > On Mon, 5 Feb 2007, Linus Torvalds wrote: > > > Indeed. One word is *exactly* what a normal system call returns too. > > > > That said, normally we have a user-space library layer to turn that into > > the "errno + return value" thing, and in the case of async() calls we > > very basically wouldn't have that. So either: > > > > - we'd need to do it in the kernel (which is actually nasty, since > > different system calls have slightly different semantics - some don't > > return any error value at all, and negative numbers are real numbers) > > > > - we'd have to teach user space about the "negative errno" mechanism, in > > which case one word really is alwats enough. > > > > Quite frankly, I much prefer the second alternative. The "negative errno" > > thing has not only worked really really well inside the kernel, it's so > > obviously 100% superior to the standard UNIX "-1 + errno" approach that > > it's not even funny. > > Currently it's in the syscall wrapper. Couldn't we have it in the > asys_teardown_stack() stub? Eeeek, that was something *really* stupid I said :D - Davide - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 0 of 4] Generic AIO by scheduling stacks
- From: Zach Brown <[email protected]>
- [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Zach Brown <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Zach Brown <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Davide Libenzi <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Zach Brown <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Davide Libenzi <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Davide Libenzi <[email protected]>
- [PATCH 0 of 4] Generic AIO by scheduling stacks
- Prev by Date: [RFC,PATCH] CELL PPU Oprofile SPU profiling updated patch
- Next by Date: Re: [PATCH 2.6.19.2] r8169: support RTL8169SC/8110SC
- Previous by thread: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- Next by thread: Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- Index(es):