public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Morris <dmorris@metavize.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
	Ben Mansell <ben@zeus.com>, Steven Dake <sdake@mvista.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: epoll reporting events when it hasn't been asked to
Date: Wed, 14 Apr 2004 13:21:03 -0700	[thread overview]
Message-ID: <407D9D2F.3010901@metavize.com> (raw)
In-Reply-To: <20040414193947.GE12105@mail.shareable.org>

Jamie Lokier wrote:

>Dirk Morris wrote:
>  
>
>>I need them to be handled like normal events. (I can explain more off 
>>list if you'd like)
>>    
>>
>
>Did you read my explanation of how to do this using the present epoll
>behaviour using _fewer_ syscalls than you are asking for?
>  
>
Ah yes, I just went back and read it.
 From what I understand you're proposing to remove the fd from the set 
lazily instead of immediately.
Which will save system calls in the cases were the HUP/ERR condition 
does not occur during the 'disabled' time.

In my case, which you may choose to disregard, this condition is not 
irregular or in any way a special case.
So the revision you have proposed is just an optimization.
You could even use this same optimization with the disable feature 
(disable it lazily) and get even better performance with the same number 
of syscalls you proposed.

I see no downside, except that it no longer conforms to the semantics of 
poll and select.
Whether or not its worth it to deviate from this behavior over such a 
detail, I don't know. :)




  reply	other threads:[~2004-04-14 20:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 18:25 epoll reporting events when it hasn't been asked to Ben Mansell
2004-04-01 19:28 ` Davide Libenzi
2004-04-01 23:29   ` Steven Dake
2004-04-02  9:04     ` Ben Mansell
2004-04-02 15:22       ` Davide Libenzi
2004-04-02 18:40         ` Is POLLHUP an input-only or bidirectional condition? (was: epoll reporting events when it hasn't been asked to) Jamie Lokier
2004-04-03 12:19           ` Is POLLHUP an input-only or bidirectional condition? Richard Kettlewell
2004-04-03 21:44           ` Is POLLHUP an input-only or bidirectional condition? (was: epoll reporting events when it hasn't been asked to) Davide Libenzi
2004-04-03 22:35             ` Jamie Lokier
2004-04-04  1:28               ` Davide Libenzi
2004-04-04  2:08                 ` Jamie Lokier
2004-04-04  2:49                   ` Davide Libenzi
2004-04-04 18:51               ` Ben Mansell
2004-04-04 19:41                 ` Davide Libenzi
2004-04-04 20:24                 ` Jamie Lokier
2004-04-14 17:59         ` epoll reporting events when it hasn't been asked to Dirk Morris
2004-04-14 19:39           ` Jamie Lokier
2004-04-14 20:21             ` Dirk Morris [this message]
2004-04-14 21:48               ` Jamie Lokier
  -- strict thread matches above, loose matches on Subject: below --
2004-04-01 16:54 Ben
2004-04-01 17:51 ` Davide Libenzi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=407D9D2F.3010901@metavize.com \
    --to=dmorris@metavize.com \
    --cc=ben@zeus.com \
    --cc=davidel@xmailserver.org \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdake@mvista.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox