From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Wong <normalperson@yhbt.net>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] epoll: trim epitem by one cache line on x86_64
Date: Wed, 6 Mar 2013 14:37:41 -0800 [thread overview]
Message-ID: <20130306143741.d5e56f13c94d2d6b2c1ea449@linux-foundation.org> (raw)
In-Reply-To: <20130304112941.GA16284@dcvr.yhbt.net>
On Mon, 4 Mar 2013 11:29:41 +0000 Eric Wong <normalperson@yhbt.net> wrote:
> It is common for epoll users to have thousands of epitems, so saving a
> cache line on every allocation leads to large memory savings.
>
> Since epitem allocations are cache-aligned, reducing sizeof(struct
> epitem) from 136 bytes to 128 bytes will allow it to squeeze under a
> cache line boundary on x86_64.
>
> >From /sys/kernel/slab/eventpoll_epi, I see the following changes on my
> x86_64 Core2 Duo (which has 64-byte cache alignment):
>
> object_size : 192 => 128
> objs_per_slab: 21 => 32
>
> I have no access to other 64-bit machines, so I am limiting this to
> x86_64-only with EPOLL_PACKED instead of __attribute__((packed))
>
> ...
>
> --- a/fs/eventpoll.c
> +++ b/fs/eventpoll.c
> @@ -107,7 +107,7 @@
> struct epoll_filefd {
> struct file *file;
> int fd;
> -};
> +} EPOLL_PACKED;
>
> /*
> * Structure used to track possible nested calls, for too deep recursions
Yes, I see the same numbers on my gcc, x86_64 allmodconfig.
It's going to be hard to maintain this - someone will change something
sometime and break it. I suppose we could add a runtime check if we
cared enough. Adding a big fat comment to struct epitem might help.
I don't see much additional room to be saved. We could probably remove
epitem.nwait, but that wouldn't actually save anything because nwait
nestles with ffd.fd.
I tested your patch on powerpc and it reduced sizeof(epitem) from 136
to 128 for that arch as well, so I suggest we run with
--- a/fs/eventpoll.c~epoll-trim-epitem-by-one-cache-line-on-x86_64-fix
+++ a/fs/eventpoll.c
@@ -105,7 +105,7 @@
struct epoll_filefd {
struct file *file;
int fd;
-} EPOLL_PACKED;
+} __packed;
/*
* Structure used to track possible nested calls, for too deep recursions
_
next prev parent reply other threads:[~2013-03-06 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 11:29 Eric Wong
2013-03-06 22:37 ` Andrew Morton [this message]
2013-03-07 10:32 ` Eric Wong
2013-03-08 23:54 ` Andrew Morton
2013-03-09 0:41 ` [PATCH] epoll: comment + BUILD_BUG_ON to prevent epitem bloat Eric Wong
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=20130306143741.d5e56f13c94d2d6b2c1ea449@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®