From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: richard@rsk.demon.co.uk, viro@zeniv.linux.org.uk
Subject: + fs-reorder-struct-inotify_device-on-64bits-to-remove-padding.patch added to -mm tree
Date: Sat, 06 Dec 2008 23:47:19 -0800 [thread overview]
Message-ID: <200812070747.mB77lJfc005342@imap1.linux-foundation.org> (raw)
The patch titled
fs: reorder struct inotify_device on 64bits to remove padding
has been added to the -mm tree. Its filename is
fs-reorder-struct-inotify_device-on-64bits-to-remove-padding.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: fs: reorder struct inotify_device on 64bits to remove padding
From: Richard Kennedy <richard@rsk.demon.co.uk>
Reorder struct inotify_device to remove 8 bytes of padding on 64bit
builds, reducing size to 128 bytes. Therefore allocating from a smaller
slab & using one fewer cachelines.
Signed-off-by: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/inotify_user.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/inotify_user.c~fs-reorder-struct-inotify_device-on-64bits-to-remove-padding fs/inotify_user.c
--- a/fs/inotify_user.c~fs-reorder-struct-inotify_device-on-64bits-to-remove-padding
+++ a/fs/inotify_user.c
@@ -76,10 +76,10 @@ struct inotify_device {
struct mutex ev_mutex; /* protects event queue */
struct mutex up_mutex; /* synchronizes watch updates */
struct list_head events; /* list of queued events */
- atomic_t count; /* reference count */
struct user_struct *user; /* user who opened this dev */
struct inotify_handle *ih; /* inotify handle */
struct fasync_struct *fa; /* async notification */
+ atomic_t count; /* reference count */
unsigned int queue_size; /* size of the queue (bytes) */
unsigned int event_count; /* number of pending events */
unsigned int max_events; /* maximum number of events */
_
Patches currently in -mm which might be from richard@rsk.demon.co.uk are
origin.patch
linux-next.patch
fs-reorder-struct-inotify_device-on-64bits-to-remove-padding.patch
reply other threads:[~2008-12-07 7:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200812070747.mB77lJfc005342@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=richard@rsk.demon.co.uk \
--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.