From: Andy Lutomirski <luto@amacapital.net>
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 11:33:30 -0800 [thread overview]
Message-ID: <52EFEF0A.9080101@amacapital.net> (raw)
In-Reply-To: <1391393832-8754-1-git-send-email-n1ght.4nd.d4y@gmail.com>
On 02/02/2014 06:17 PM, Nathaniel Yazdani wrote:
> Hi everyone,
>
> This patch series adds support for read(), write(), and ioctl() operations
> on eventpolls as well as an associated userspace structure to format the
> eventpoll entries delivered via read()/write() buffers. The new structure,
> struct epoll, differs from struct epoll_event mainly in that it also holds
> the associated file descriptor. Using the normal I/O interface to manipulate
> eventpolls is much neater than using epoll-specific syscalls while also
> allowing for greater flexibility (theoretically, pipes could be used to
> filter access). Specifically, write() creates, modifies, and/or removes event
> entries stored in the supplied buffer, using the userspace identifier to
> check whether an entry exists and removing it if no events are set to trigger
> it, while read() simply waits for enough events to fill the provided buffer.
> As timeout control is essential for polling to be practical, ioctl() is used
> to configure an optional timeout, which is infinite by default.
If major changes are made to the epoll API, I want a way to do a bunch
of EPOLL_CTL_MODs and a wait, all in one syscall. Even better: allow
more flexible timeouts (CLOCK_MONOTONIC, CLOCK_REALTIME, etc) at the
same time.
Since this can't do that, I'm not terribly inspired.
--Andy
>
> Documentation/ioctl/ioctl-number.txt | 1 +
> fs/eventpoll.c | 534 ++++++++++++++++++++++++-----------
> include/uapi/linux/eventpoll.h | 10 +
> 3 files changed, 384 insertions(+), 161 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-02-03 19:33 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 ` [RFC PATCH 0/3] epoll: read(),write(),ioctl() interface Clemens Ladisch
2014-02-03 19:34 ` Nathaniel Yazdani
2014-02-03 19:33 ` Andy Lutomirski [this message]
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=52EFEF0A.9080101@amacapital.net \
--to=luto@amacapital.net \
--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