From: Qiang Huang <h.huangqiang@huawei.com>
To: cgroups@vger.kernel.org, linux-mm@kvack.org
Cc: handai.szj@taobao.com, lizefan@huawei.com,
nishimura@mxp.nes.nec.co.jp, akpm@linux-foundation.org,
mhocko@suse.cz, jeff.liu@oracle.com
Subject: [PATCH 4/4] memcg: reduce function dereference
Date: Wed, 31 Jul 2013 15:31:25 +0800 [thread overview]
Message-ID: <1375255885-10648-5-git-send-email-h.huangqiang@huawei.com> (raw)
In-Reply-To: <1375255885-10648-1-git-send-email-h.huangqiang@huawei.com>
This function dereferences res far too often, so optimize it.
Signed-off-by: Sha Zhengju <handai.szj@taobao.com>
Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
---
kernel/res_counter.c | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/kernel/res_counter.c b/kernel/res_counter.c
index 085d3ae..4aa8a30 100644
--- a/kernel/res_counter.c
+++ b/kernel/res_counter.c
@@ -178,27 +178,30 @@ u64 res_counter_read_u64(struct res_counter *counter, int member)
#endif
int res_counter_memparse_write_strategy(const char *buf,
- unsigned long long *res)
+ unsigned long long *resp)
{
char *end;
+ unsigned long long res;
/* return RES_COUNTER_MAX(unlimited) if "-1" is specified */
if (*buf == '-') {
- *res = simple_strtoull(buf + 1, &end, 10);
- if (*res != 1 || *end != '\0')
+ res = simple_strtoull(buf + 1, &end, 10);
+ if (res != 1 || *end != '\0')
return -EINVAL;
- *res = RES_COUNTER_MAX;
+ *resp = RES_COUNTER_MAX;
return 0;
}
- *res = memparse(buf, &end);
+ res = memparse(buf, &end);
if (*end != '\0')
return -EINVAL;
- if (PAGE_ALIGN(*res) >= *res)
- *res = PAGE_ALIGN(*res);
+ if (PAGE_ALIGN(res) >= res)
+ res = PAGE_ALIGN(res);
else
- *res = RES_COUNTER_MAX;
+ res = RES_COUNTER_MAX;
+
+ *resp = res;
return 0;
}
--
1.8.3
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-07-31 7:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 7:31 [PATCH 0/4] memcg: fix memcg resource limit overflow issues Qiang Huang
2013-07-31 7:31 ` [PATCH 1/4] memcg: correct RESOURCE_MAX to ULLONG_MAX Qiang Huang
2013-07-31 8:00 ` Michal Hocko
2013-07-31 7:31 ` [PATCH 2/4] memcg: rename RESOURCE_MAX to RES_COUNTER_MAX Qiang Huang
2013-07-31 8:02 ` Michal Hocko
2013-07-31 7:31 ` [PATCH 3/4] memcg: avoid overflow caused by PAGE_ALIGN Qiang Huang
2013-07-31 8:14 ` Michal Hocko
2013-07-31 7:31 ` Qiang Huang [this message]
2013-07-31 8:20 ` [PATCH 4/4] memcg: reduce function dereference Michal Hocko
2013-07-31 8:23 ` [PATCH 0/4] memcg: fix memcg resource limit overflow issues Sha Zhengju
2013-07-31 8:51 ` Qiang Huang
2013-07-31 8:54 ` Li Zefan
2013-07-31 9:02 ` Qiang Huang
2013-07-31 9:34 ` Jeff Liu
2013-07-31 9:51 ` Li Zefan
2013-07-31 9:39 ` Sha Zhengju
2013-07-31 9:50 ` Michal Hocko
2013-07-31 10:04 ` Sha Zhengju
2013-07-31 9:51 ` Qiang Huang
2013-07-31 9:28 ` Sha Zhengju
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=1375255885-10648-5-git-send-email-h.huangqiang@huawei.com \
--to=h.huangqiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=handai.szj@taobao.com \
--cc=jeff.liu@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.cz \
--cc=nishimura@mxp.nes.nec.co.jp \
/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).