RE: Use of asynchronous receive at kernel level
RE: Use of asynchronous receive at kernel level
- Subject: RE: Use of asynchronous receive at kernel level
- From: "Eddy Quicksall" <email@hidden>
- Date: Thu, 15 May 2008 22:01:33 -0400
But there is only one upcall function per socket and there does not seem to be
any way to tell what the upcall is for. Is there something I’m missing?
Eddy
From: Josh Graessley
[mailto:email@hidden]
Sent: Monday, April 14, 2008 1:51
PM
To: Eddy
Quicksall
Cc: email@hidden
Subject: Re: Use of asynchronous
receive at kernel level
When you create the socket you have the option of specifying and upcall
function. That upcall function will be called when data is ready and waiting.
Look in kpi_socket.h.
On Mar 24, 2008, at 1:02 PM, Eddy Quicksall
wrote:
I need to use the kernel level sockets
routines asynchronously (i.e., non blocking). The will normally need a callback
when data is available so I can call soreceive to extract the data from the
kernel mbuf’s.
I can see how to call soreceive but I
can’t see how to get an upcall when data is available.
Does anyone have any information on this?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden