RE: Asynchronous sock_sendmbuf
RE: Asynchronous sock_sendmbuf
- Subject: RE: Asynchronous sock_sendmbuf
- From: "Eddy Quicksall" <email@hidden>
- Date: Thu, 22 May 2008 13:44:36 -0400
Can you please give me a pointer to the document? I'm doing something
similar to you.
Eddy
-----Original Message-----
From: darwin-kernel-bounces+quicksall_temp=email@hidden
[mailto:darwin-kernel-bounces+quicksall_temp=email@hidden]
On Behalf Of Igor Mikushkin
Sent: Thursday, May 22, 2008 4:27 AM
To: email@hidden
Subject: Re: Asynchronous sock_sendmbuf
2008/5/22 Terry Lambert <email@hidden>:
> On May 22, 2008, at 12:05 AM, Igor Mikushkin wrote:
>>
>> 2008/5/22 Terry Lambert <email@hidden>:
>>>
>>> Maybe we can step back a second...
>>>
>>> What are you trying to accomplish here that you think getting an upcall
>>> would accomplish for you?
>>
>> I'm trying to understand how to work with kernel sockets in a proper way.
>> I decided to follow the rule: first upcall is always response to
>> sock_connect, the others are receive upcalls (even if they are not).
>>
>> The truth of this rule is my main question related to upcall.
>
> You realize that if it's not documented, it's not supported, and even if
you
> find out that something currently works, if you depend on it, there's no
> guarantee that your application will still work after the next software
> update if you use what you discover, right?
>
It looks to me like the kernel socket documentation is very contradictory.
The only example it provides (see NKE guide) uses a non-blocking socket.
Upcall is used for only receive there. And I think it's OK.
So I think this should work on later OS releases too and this is preferable
way.
In spite of it the related documentation is just absent.
I was falsely thinking that blocking send operation give me much more
guaranties that non-blocking one.
I was supposed that blocking call returns only when an operation is
actually completes.
So I was going to introduce the same guaranties with upcall.
That is why the topic is called asynchronous sock_sendmbuf.
Now I think that this is false.
So I don't need send upcall at all, only receive.
Anyway I'm sure I should know when upcall can be invoked.
Igor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
uth.net
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