From: Roman Penyaev <rpenyaev@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Davidlohr Bueso <dbueso@suse.de>, Jason Baron <jbaron@akamai.com>,
Al Viro <viro@zeniv.linux.org.uk>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrea Parri <andrea.parri@amarulasolutions.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 02/13] epoll: introduce user structures for polling from userspace
Date: Tue, 22 Jan 2019 12:46:55 +0100 [thread overview]
Message-ID: <891cb81595dbad8b90cbb6de940da97f@suse.de> (raw)
In-Reply-To: <CAHk-=wh16im2u1fHcZgMa-Z19Ri=UD2aY+r9=1rO4hginjcnBQ@mail.gmail.com>
On 2019-01-21 22:34, Linus Torvalds wrote:
> So I'm not entirely convinced, but I guess actual numbers and users
> might convince me otherwise.
>
> However, a quick comment:
>
> On Tue, Jan 22, 2019 at 9:15 AM Roman Penyaev <rpenyaev@suse.de> wrote:
>>
>> +struct epoll_uitem {
>> + __poll_t ready_events;
>> + struct epoll_event event;
>> +};
>
> This really ends up being a horrible data structure.
>
> struct epoll_event is declared as
>
> struct epoll_event {
> __poll_t events;
> __u64 data;
> } EPOLL_PACKED;
>
> and __poll_t is "unsigned". So on pretty much all 64-bit architectures
> except for x86-64 (which sets that packed attribute), you have a
> packing hole there in between the events and the data, and "struct
> epoll_event" has 8-byte alignment.
>
> Now, in "struct epoll_uitem", you end up having *another* packing hold
> in between "ready_events" and "struct epoll_event".
>
> So this data structure that has 16 bytes of actual data, ends up being
> 24 bytes in size.
>
> Again, x86-64 happens to be the exception to this, but that's a random
> small implementation detail, not a design thing.
>
> I think "struct epoll_event" was badly designed to begin with to have
> this issue, but it shouldn't then be an excuse to make things even
> worse with this array of "struct epoll_uitem" things.
>
> Hmm?
Ha! Yes, you are right. Eyes see "packed" and brain responds
"ok, this is 12 bytes, + 4 for ready_events = 16, perfect".
I have not paid any attention to how actually this EPOLL_PACKED is
defined. Not nice at all. I will unfold the structure like this:
/*
* Item, shared with userspace. Unfortunately we can't embed
epoll_event
* structure, because it is badly aligned on all 64-bit archs, except
* x86-64 (see EPOLL_PACKED). sizeof(epoll_uitem) == 16
*/
struct epoll_uitem {
__poll_t ready_events;
__poll_t events;
__u64 data;
};
Also BUILD_BUG_ON(sizeof(epoll_uitem) != 16) somewhere in alloc won't
hurt.
--
Roman
next prev parent reply other threads:[~2019-01-22 11:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 20:14 [RFC PATCH v2 00/13] epoll: support pollable epoll from userspace Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 01/13] epoll: move private helpers from a header to the source Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 02/13] epoll: introduce user structures for polling from userspace Roman Penyaev
2019-01-21 21:34 ` Linus Torvalds
2019-01-22 11:46 ` Roman Penyaev [this message]
2019-01-21 20:14 ` [RFC PATCH v2 03/13] epoll: allocate user header and user events ring " Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 04/13] epoll: some sanity flags checks for epoll syscalls " Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 05/13] epoll: offload polling to a work in case of epfd polled " Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 06/13] epoll: introduce helpers for adding/removing events to uring Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 07/13] epoll: call ep_add_event_to_uring() from ep_poll_callback() Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 08/13] epoll: support polling from userspace for ep_insert() Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 09/13] epoll: support polling from userspace for ep_remove() Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 10/13] epoll: support polling from userspace for ep_modify() Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 11/13] epoll: support polling from userspace for ep_poll() Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 12/13] epoll: support mapping for epfd when polled from userspace Roman Penyaev
2019-01-21 20:14 ` [RFC PATCH v2 13/13] epoll: implement epoll_create2() syscall Roman Penyaev
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=891cb81595dbad8b90cbb6de940da97f@suse.de \
--to=rpenyaev@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andrea.parri@amarulasolutions.com \
--cc=dbueso@suse.de \
--cc=jbaron@akamai.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--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).