Re: async i/o question
- From: Rainer Weikusat <rweikusat@xxxxxxxxxxx>
- Date: Sun, 04 Nov 2007 14:15:19 +0100
anatolik <anatolik@xxxxxxxxx> writes:
Ehh ... assuming you state your requirements correctly (and
completely), this is ordinary 'blocking' synchronous I/O, which
happens to be the default behaviour of the respective primitives
(read/ write/ send/ recv usf).
The requerements are correct, the application should send several
buffers to kernel module. Kernel mode fills the buffers when it has
data, the application processes the buffers when it gets cpu time and
sends buffers back.
THIS IS ORDINARY 'BLOCKING' SYNCHRONOUS I/O.
Hint: You are asking the stupid question, not me.
.
- Follow-Ups:
- Re: async i/o question
- From: anatolik
- Re: async i/o question
- References:
- async i/o question
- From: anatolik
- Re: async i/o question
- From: Rainer Weikusat
- Re: async i/o question
- From: anatolik
- async i/o question
- Prev by Date: Re: USB SET_DESCRIPTOR_TO_DEVICE ??
- Next by Date: Re: ----About too much global variables
- Previous by thread: Re: async i/o question
- Next by thread: Re: async i/o question
- Index(es):
Relevant Pages
|