From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: akpm@linux-foundation.org, vdavydov.dev@gmail.com,
penguin-kernel@I-love.SAKURA.ne.jp, chris@chris-wilson.co.uk,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
ktkhai@virtuozzo.com
Subject: [PATCH 1/2] mm: Keep int fields in struct shrink_control together
Date: Thu, 19 Jul 2018 13:51:19 +0300 [thread overview]
Message-ID: <153199747930.21131.861043607301997810.stgit@localhost.localdomain> (raw)
In-Reply-To: <153199724495.21131.9248876333336922199.stgit@localhost.localdomain>
gfp_t is of unsigned type, so let's move nid to keep
them together.
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
---
include/linux/shrinker.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/shrinker.h b/include/linux/shrinker.h
index b154fd2b084c..d58aaaed34a4 100644
--- a/include/linux/shrinker.h
+++ b/include/linux/shrinker.h
@@ -12,6 +12,9 @@
struct shrink_control {
gfp_t gfp_mask;
+ /* current node being shrunk (for NUMA aware shrinkers) */
+ int nid;
+
/*
* How many objects scan_objects should scan and try to reclaim.
* This is reset before every call, so it is safe for callees
@@ -26,9 +29,6 @@ struct shrink_control {
*/
unsigned long nr_scanned;
- /* current node being shrunk (for NUMA aware shrinkers) */
- int nid;
-
/* current memcg being shrunk (for memcg aware shrinkers) */
struct mem_cgroup *memcg;
};
next prev parent reply other threads:[~2018-07-19 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 10:51 [PATCH 0/2] Reorderings in struct shrinker and struct shrink_control Kirill Tkhai
2018-07-19 10:51 ` Kirill Tkhai [this message]
2018-07-19 11:10 ` [PATCH 1/2] mm: Keep int fields in struct shrink_control together Michal Hocko
2018-07-19 11:14 ` Kirill Tkhai
2018-07-19 10:51 ` [PATCH 2/2] mm: Make flags of unsigned type in struct shrinker Kirill Tkhai
2018-07-19 11:14 ` Michal Hocko
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=153199747930.21131.861043607301997810.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=vdavydov.dev@gmail.com \
/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®