linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Nathaniel Yazdani <n1ght.4nd.d4y@gmail.com>, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] epoll: read(),write(),ioctl() interface
Date: Mon, 03 Feb 2014 10:43:42 +0100	[thread overview]
Message-ID: <52EF64CE.90506@ladisch.de> (raw)
In-Reply-To: <1391393832-8754-1-git-send-email-n1ght.4nd.d4y@gmail.com>

Nathaniel Yazdani wrote:
> Using the normal I/O interface to manipulate eventpolls is much neater
> than using epoll-specific syscalls

But it introduces a _second_ API, which is epoll-specific too, and does
not use the standard semantics either.

> while also allowing for greater flexibility (theoretically, pipes could
> be used to filter access).

I do not understand this.

> read() simply waits for enough events to fill the provided buffer.

The usual semantics of read() are to return a partially filled buffer if
it would block otherwise, i.e., blocking is done only if the returned
buffer would have been empty.

> As timeout control is essential for polling to be practical, ioctl() is
> used to configure an optional timeout

This is what the timeout parameter of poll() and friends is for.


Regards,
Clemens

  parent reply	other threads:[~2014-02-03  9:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03  2:17 [RFC PATCH 0/3] epoll: read(),write(),ioctl() interface Nathaniel Yazdani
2014-02-03  2:17 ` [RFC PATCH 1/3] epoll: reserve small ioctl() space Nathaniel Yazdani
2014-02-03  2:17 ` [RFC PATCH 2/3] epoll: add struct epoll & ioctl() commands Nathaniel Yazdani
2014-02-03  2:17 ` [RFC PATCH 3/3] epoll: add read()/write()/ioctl() operations Nathaniel Yazdani
2014-02-03  9:43 ` Clemens Ladisch [this message]
2014-02-03 19:34   ` [RFC PATCH 0/3] epoll: read(),write(),ioctl() interface Nathaniel Yazdani
2014-02-03 19:33 ` Andy Lutomirski
2014-02-03 19:42   ` Nathaniel Yazdani
2014-02-03 19:56     ` Andy Lutomirski
2014-02-03 21:51       ` Eric Wong
2014-02-03 22:06         ` Andy Lutomirski
  -- strict thread matches above, loose matches on Subject: below --
2014-02-03  0:30 Nathaniel Yazdani

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=52EF64CE.90506@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n1ght.4nd.d4y@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).