From: Eric Wong <normalperson@yhbt.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] epoll: comment + BUILD_BUG_ON to prevent epitem bloat
Date: Sat, 9 Mar 2013 00:41:07 +0000 [thread overview]
Message-ID: <20130309004107.GA31085@dcvr.yhbt.net> (raw)
In-Reply-To: <20130308155410.3c63f24ee28e6532006cb0d4@linux-foundation.org>
This will prevent us from accidentally introducing a memory bloat
regression here in the future.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Cc: Al Viro <viro@ZenIV.linux.org.uk>
---
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 7 Mar 2013 10:32:40 +0000 Eric Wong <normalperson@yhbt.net> wrote:
>
> > Andrew Morton <akpm@linux-foundation.org> wrote:
> > > 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.
> >
> > Thanks for looking at this patch. I'll send a patch with a comment
> > about keeping epitem size in check. Also, would adding (with comments):
> >
> > BUILD_BUG_ON(sizeof(struct epitem) > 128);
> >
> > ...be too heavy-handed? I used that in my testing. I'll check for:
> > sizeof(void *) <= 8 too; in case 128-bit machines appear...
>
> I guess such a check might avoid accidents in the future. If it
> becomes a problem, we can always delete it.
fs/eventpoll.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/fs/eventpoll.c b/fs/eventpoll.c
index 9fec183..55028da 100644
--- a/fs/eventpoll.c
+++ b/fs/eventpoll.c
@@ -128,6 +128,8 @@ struct nested_calls {
/*
* Each file descriptor added to the eventpoll interface will
* have an entry of this type linked to the "rbr" RB tree.
+ * Avoid increasing the size of this struct, there can be many thousands
+ * of these on a server and we do not want this to take another cache line.
*/
struct epitem {
/* RB tree node used to link this structure to the eventpoll RB tree */
@@ -1964,6 +1966,12 @@ static int __init eventpoll_init(void)
/* Initialize the structure used to perform file's f_op->poll() calls */
ep_nested_calls_init(&poll_readywalk_ncalls);
+ /*
+ * We can have many thousands of epitems, so prevent this from
+ * using an extra cache line on 64-bit (and smaller) CPUs
+ */
+ BUILD_BUG_ON(sizeof(void *) <= 8 && sizeof(struct epitem) > 128);
+
/* Allocates slab cache used to allocate "struct epitem" items */
epi_cache = kmem_cache_create("eventpoll_epi", sizeof(struct epitem),
0, SLAB_HWCACHE_ALIGN | SLAB_PANIC, NULL);
--
Eric Wong
prev parent reply other threads:[~2013-03-09 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 11:29 [PATCH] epoll: trim epitem by one cache line on x86_64 Eric Wong
2013-03-06 22:37 ` Andrew Morton
2013-03-07 10:32 ` Eric Wong
2013-03-08 23:54 ` Andrew Morton
2013-03-09 0:41 ` Eric Wong [this message]
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=20130309004107.GA31085@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®