From: Martin Sustrik <sustrik@250bpm.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Sha Zhengju <handai.szj@taobao.com>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] eventfd: implementation of EFD_MASK flag
Date: Sat, 09 Feb 2013 13:04:27 +0100 [thread overview]
Message-ID: <522eddabbd205305038fef897d283f26@webmail.moloch.sk> (raw)
In-Reply-To: <20130209115149.GA15636@dcvr.yhbt.net>
On 2013-02-09 12:51, Eric Wong wrote:
> Yes, your eventfd change is probably the best way if you want/need
> to only watch a subset of your sockets, especially if you want
> poll/select to be an option.
Yes, the poll/select thing is the important point.
I wouldn't care if the only problem was that I, as the protocol
implementer, would have to implement some kind of workaround in my
protocol library. The problem is that these convoluted semantics leak --
through the use of poll, select et al. -- to the end user.
From my personal experience I can say that end users have pretty hard
time using such complex workarounds instead of simply using a native
file descriptor with standardised semantics.
Martin
next prev parent reply other threads:[~2013-02-09 12:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 6:41 [PATCH 1/1] eventfd: implementation of EFD_MASK flag Martin Sustrik
2013-02-07 19:12 ` Andy Lutomirski
2013-02-07 20:11 ` Martin Sustrik
2013-02-08 1:03 ` Andy Lutomirski
2013-02-08 5:26 ` Martin Sustrik
2013-02-08 6:36 ` Andy Lutomirski
2013-02-08 6:55 ` Martin Sustrik
2013-02-08 22:08 ` Eric Wong
2013-02-09 3:26 ` Martin Sustrik
2013-02-07 22:44 ` Andrew Morton
2013-02-07 23:30 ` Martin Sustrik
2013-02-08 12:43 ` Martin Sustrik
2013-02-08 22:21 ` Eric Wong
2013-02-09 2:40 ` Martin Sustrik
2013-02-09 3:54 ` Eric Wong
2013-02-09 7:36 ` Martin Sustrik
2013-02-09 11:51 ` Eric Wong
2013-02-09 12:04 ` Martin Sustrik [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-07 23:29 Martin Sustrik
2013-02-15 2:45 ` Michał Mirosław
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=522eddabbd205305038fef897d283f26@webmail.moloch.sk \
--to=sustrik@250bpm.com \
--cc=akpm@linux-foundation.org \
--cc=handai.szj@taobao.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=normalperson@yhbt.net \
--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).