On Fri, 2 Feb 2007, Ingo Molnar wrote: > > but if the application /has/ identified fundamental parallelism, we > /must not/ shut that parallelism off by /designing/ this interface to > use the fibril thing which is a limited cooperative, single-CPU entity. Right. We should for example encourage people to use some kind of paralellizing construct. I know! We could even call them "threads", so to give people the idea that they are independent smaller entities in a thicker "rope", and we could call that bigger entity a "task" or "process", since it "processes" data. Or is that just too far out? Linus - 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/
- Follow-Ups:
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- From: Linus Torvalds <[email protected]>
- Re: [PATCH 2 of 4] Introduce i386 fibril scheduling
- 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: Alan <[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: Alan <[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]>
- [PATCH 0 of 4] Generic AIO by scheduling stacks
- Prev by Date: Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- Next by Date: Re: [PATCH] mm: remove global locks from mm/highmem.c
- 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):
 |