From: Damian Hobson-Garcia <dhobsong@igel.co.jp>
To: Martin Sustrik <sustrik@250bpm.com>
Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
netdev@vger.kernel.org, David.Laight@aculab.com
Subject: Re: [PATCH v2 1/1] eventfd: implementation of EFD_MASK flag
Date: Wed, 16 Sep 2015 16:43:58 +0900 [thread overview]
Message-ID: <55F91DBE.90903@igel.co.jp> (raw)
In-Reply-To: <70093385dc00b108e16862c8b8b1c13c@imap.lucina.net>
Hi Martin,
On 2015-09-16 3:51 PM, Martin Sustrik wrote:
> On 2015-09-16 08:27, Damian Hobson-Garcia wrote:
>>
>> Additionally, to provide a way to associate user-space state with eventfd
>> object, it allows to attach user-space data to the file descriptor.
>
> The above paragraph is a leftover from the past. The functionality no
> longer exist.
>
Oops, I forgot to delete that part. I'll get rid of it.
>>
>> The semantics of EFD_MASK are as follows:
>>
>> eventfd(2):
>>
>> If eventfd is created with EFD_MASK flag set, it is initialised in such a
>> way as to signal no events on the file descriptor when it is polled on.
>> The 'initval' argument is ignored.
>>
>> write(2):
>>
>> User is allowed to write only buffers containing the following structure:
>>
>> struct efd_mask {
>> uint32_t events;
>> };
>
> Is it worth having a struct here? Why not just uint32_t?
As it stands right now, no, the struct doesn't really add anything.
uint32_t should be just fine.
>
> Martin
Damian
next prev parent reply other threads:[~2015-09-16 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 6:27 [PATCH v2 0/1] Generalize poll events from eventfd Damian Hobson-Garcia
[not found] ` <1442384836-13045-1-git-send-email-dhobsong-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
2015-09-16 6:27 ` [PATCH v2 1/1] eventfd: implementation of EFD_MASK flag Damian Hobson-Garcia
2015-09-16 6:27 ` Damian Hobson-Garcia
2015-09-16 6:51 ` Martin Sustrik
2015-09-16 7:43 ` Damian Hobson-Garcia [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-08 8:11 Martin Sustrik
2013-02-14 22:54 ` Andrew Morton
2013-02-14 23:57 ` Andy Lutomirski
2013-02-15 3:42 ` Martin Sustrik
2013-02-15 5:24 ` Andrew Morton
2013-02-15 17:32 ` Andy Lutomirski
2013-02-15 18:37 ` Martin Sustrik
2013-02-18 8:54 ` Martin Sustrik
2013-02-18 11:57 ` Martin Sustrik
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=55F91DBE.90903@igel.co.jp \
--to=dhobsong@igel.co.jp \
--cc=David.Laight@aculab.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sustrik@250bpm.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 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.