On Wed, 28 Feb 2007, Eric Dumazet wrote:
> On Tuesday 27 February 2007 17:03, Davide Libenzi wrote:
> > On Tue, 27 Feb 2007, Eric Dumazet wrote:
> > > On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
> > > > Epoll is doing multiple passes over the ready set at the moment,
> > > > because
On Tuesday 27 February 2007 17:03, Davide Libenzi wrote:
> On Tue, 27 Feb 2007, Eric Dumazet wrote:
> > On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
> > > Epoll is doing multiple passes over the ready set at the moment,
> > > because of the constraints over the f_op->poll() call.
On Tuesday 27 February 2007 17:03, Davide Libenzi wrote:
On Tue, 27 Feb 2007, Eric Dumazet wrote:
On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
Epoll is doing multiple passes over the ready set at the moment,
because of the constraints over the f_op-poll() call. Looking at the
On Wed, 28 Feb 2007, Eric Dumazet wrote:
On Tuesday 27 February 2007 17:03, Davide Libenzi wrote:
On Tue, 27 Feb 2007, Eric Dumazet wrote:
On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
Epoll is doing multiple passes over the ready set at the moment,
because of the
On Tue, 27 Feb 2007, Eric Dumazet wrote:
> On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
> > Epoll is doing multiple passes over the ready set at the moment, because
> > of the constraints over the f_op->poll() call. Looking at the code again,
> > I noticed that we already hold the
On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
> Epoll is doing multiple passes over the ready set at the moment, because
> of the constraints over the f_op->poll() call. Looking at the code again,
> I noticed that we already hold the epoll semaphore in read, and this
> (together with
On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
Epoll is doing multiple passes over the ready set at the moment, because
of the constraints over the f_op-poll() call. Looking at the code again,
I noticed that we already hold the epoll semaphore in read, and this
(together with other
On Tue, 27 Feb 2007, Eric Dumazet wrote:
On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
Epoll is doing multiple passes over the ready set at the moment, because
of the constraints over the f_op-poll() call. Looking at the code again,
I noticed that we already hold the epoll
On Mon, 26 Feb 2007, Linus Torvalds wrote:
> On Mon, 26 Feb 2007, Davide Libenzi wrote:
> >
> > Epoll is doing multiple passes over the ready set at the moment, because
> > of the constraints over the f_op->poll() call. Looking at the code again,
> > I noticed that we already hold the epoll
On Mon, 26 Feb 2007, Davide Libenzi wrote:
>
> Epoll is doing multiple passes over the ready set at the moment, because
> of the constraints over the f_op->poll() call. Looking at the code again,
> I noticed that we already hold the epoll semaphore in read, and this
> (together with other
Epoll is doing multiple passes over the ready set at the moment, because
of the constraints over the f_op->poll() call. Looking at the code again,
I noticed that we already hold the epoll semaphore in read, and this
(together with other locking conditions that hold while doing an
Epoll is doing multiple passes over the ready set at the moment, because
of the constraints over the f_op-poll() call. Looking at the code again,
I noticed that we already hold the epoll semaphore in read, and this
(together with other locking conditions that hold while doing an
epoll_wait())
On Mon, 26 Feb 2007, Davide Libenzi wrote:
Epoll is doing multiple passes over the ready set at the moment, because
of the constraints over the f_op-poll() call. Looking at the code again,
I noticed that we already hold the epoll semaphore in read, and this
(together with other locking
On Mon, 26 Feb 2007, Linus Torvalds wrote:
On Mon, 26 Feb 2007, Davide Libenzi wrote:
Epoll is doing multiple passes over the ready set at the moment, because
of the constraints over the f_op-poll() call. Looking at the code again,
I noticed that we already hold the epoll semaphore in
14 matches
Mail list logo
