All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Langley <alangley@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Edge triggered epoll with pts devices acts as level triggered
Date: Fri, 12 Aug 2005 12:19:39 +0100	[thread overview]
Message-ID: <396556a20508120419238abca6@mail.gmail.com> (raw)

(please cc me on replies)

Waiting for edge triggered events (with EPOLLET) on pseudo terminal
devices appears to act as if it were level triggered; when data is
ready the fd is always returned by epoll_wait.

You can test this with the code below. Compile, run and press return.
If edge triggering is working correctly a single event will be
generated, otherwise a never ending stream will start.

This works *correctly* at a real terminal, but fails for pseudo
terminals (specifically an xterm). As far as I can test with other
terminals and ssh this is a general problem with pseudo terminals.

% uname -a
Linux ice 2.6.12 #4 SMP Sun Jul 31 11:42:15 BST 2005 i686 Pentium II
(Deschutes) GenuineIntel GNU/Linux
(vanilla kernel sources)

% cat et2.c
#include <sys/epoll.h>
#include <unistd.h>
#include <string.h>

int
main(int argc, char **argv) {
        const int epoll_fd = epoll_create(4);
        struct epoll_event ev;
        struct epoll_event events[4];

        memset(&ev, 0, sizeof(ev));
        ev.events = EPOLLIN | EPOLLET;

        epoll_ctl(epoll_fd, EPOLL_CTL_ADD, 0, &ev);

        for (;;) {
                epoll_wait(epoll_fd, events, 4, -1);
                write(1, ".", 1);
        }
}


Thanks


AGL

-- 
Adam Langley                                      agl@imperialviolet.org
http://www.imperialviolet.org                       (+44) (0)7906 332512
PGP: 9113   256A   CC0F   71A6   4C84   5087   CDA5   52DF   2CB6   3D60

             reply	other threads:[~2005-08-12 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12 11:19 Adam Langley [this message]
2005-08-12 17:30 ` Edge triggered epoll with pts devices acts as level triggered Adam Langley
2005-08-13 10:30 ` Heikki Orsila

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=396556a20508120419238abca6@mail.gmail.com \
    --to=alangley@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.