Re: kern_control KPI and socket reads
Re: kern_control KPI and socket reads
- Subject: Re: kern_control KPI and socket reads
- From: "Bhavesh Davda" <email@hidden>
- Date: Thu, 15 Mar 2007 13:39:46 -0700
On 3/15/07, Michael Smith <email@hidden> wrote:
On Mar 15, 2007, at 10:14 AM, Bhavesh Davda wrote:
> Yeah, I was trying to avoid having 2 system calls for every read(2): a
> read(2) and an ioctl(2)/setsockopt(2), to get this functionality.
What "functionality" are you actually trying to achieve?
There are control flow models available for most reasonable
behaviours already; it feels like you have decided on one that
history has so far rejected...
All I would like is the ability to run some code in my NKE when the
queue that I was sending mbufs to via ctl_enqueuembuf() has been
drained. Now one could argue that this "code" doesn't have to be in
the NKE and why doesn't the user app doing the read(2) run this code
when read returns EAGAIN. Just suffice it to say that what I'm doing
is fairly specialized and I don't know of a historical precedent that
fits the pattern.
That's why I tried to boil down the question to a simple one.
Thanks!
--
Bhavesh P. Davda
_______________________________________________
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