[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20061221165143.GA322@2ka.mipt.ru>
Date: Thu, 21 Dec 2006 19:51:43 +0300
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: jamal <hadi@...erus.ca>
Cc: Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
David Miller <davem@...emloft.net>,
Ulrich Drepper <drepper@...hat.com>,
Andrew Morton <akpm@...l.org>, netdev <netdev@...r.kernel.org>,
Zach Brown <zach.brown@...cle.com>,
Christoph Hellwig <hch@...radead.org>,
Chase Venters <chase.venters@...entec.com>,
Johann Borck <johann.borck@...sedata.com>
Subject: Re: [take28-resend_1->0 0/8] kevent: Generic event handling mechanism.
On Thu, Dec 21, 2006 at 11:42:04AM -0500, jamal (hadi@...erus.ca) wrote:
> > > > Things like sockets/pipes can only benefit from direct kevent usage
> > > > instead of ->poll() and wrappers.
> > >
> > > You should be able change it to use those schemes when it detects
> > > that the kernel supports them.
> >
> > I.e. stat() for each new file descriptor - note, that _you_ asked it :)
>
> Didnt follow. Is there some issue with libevent you mean?
libevent provides file descriptor without any additional info about it -
so when it is added into the waiting subsystem, userspace must select
different usage cases (i.e. different kevent notifications for different
types of file descriptor - socket notifications for sockets and pipes,
poll/select for all others), this requires stat() call per provided file
descriptor.
Event addition/waiting itself is the same - only parameters (type and
requested event) are changed.
> cheers,
> jamal
--
Evgeniy Polyakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists