On Mon, Aug 29, 2011 at 05:23:15PM -0700, John-Mark Gurney wrote:
> Luigi Rizzo wrote this message on Fri, Aug 26, 2011 at 23:01 +0200:
> > The other thing i need (but i believe i know how to handle it)
> > is tell whether .f_event() is called by KNOTE() or by kqueue_scan(),
> > but i believe i can
Luigi Rizzo wrote this message on Fri, Aug 26, 2011 at 23:01 +0200:
> The other thing i need (but i believe i know how to handle it)
> is tell whether .f_event() is called by KNOTE() or by kqueue_scan(),
> but i believe i can use the "hint" argument to tell the two.
Why do you need to know the dif
On Fri, Aug 26, 2011 at 01:13:03PM -0400, John Baldwin wrote:
> On Friday, August 26, 2011 11:39:40 am Luigi Rizzo wrote:
> > a question for the kqueue experts out there:
> >
> > I am trying to add kqueue support to a device driver, and am puzzled
> > on what the .f_event() function may assume.
>
On Friday, August 26, 2011 11:39:40 am Luigi Rizzo wrote:
> a question for the kqueue experts out there:
>
> I am trying to add kqueue support to a device driver, and am puzzled
> on what the .f_event() function may assume.
>
> I see that some of the examples (e.g. bpf, audit_pipe.c)
> expect tha
a question for the kqueue experts out there:
I am trying to add kqueue support to a device driver, and am puzzled
on what the .f_event() function may assume.
I see that some of the examples (e.g. bpf, audit_pipe.c)
expect that the function is called with the device lock held
(and even have a LOCK
