From: Michal Marek <mmarek@suse.cz>
To: Jianyu Zhan <nasa4836@gmail.com>
Cc: akpm@linux-foundation.org, michael.opdenacker@free-electrons.com,
tkhai@yandex.ru, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org
Subject: Re: [PATCH] scripts/tags.sh: add regular expression replacement pattern for memcg
Date: Wed, 16 Apr 2014 23:24:06 +0200 [thread overview]
Message-ID: <534EF4F6.8000900@suse.cz> (raw)
In-Reply-To: <1397134732-29106-1-git-send-email-nasa4836@gmail.com>
Dne 10.4.2014 14:58, Jianyu Zhan napsal(a):
> Sorry, the comment in previous patch is somewhat misguiding, this patch
> replaces that one.
>
> Currently, no regular expression replacement patterns for PageCgroup*
> flag-ops are defined, which causes quite a few pain while reading code.
> Just get rid of it.
>
> Also, add a comment to inform people to add pattern for whatever new
> flag-ops they add.
>
> Signed-off-by: Jianyu Zhan <nasa4836@gmail.com>
> ---
> include/linux/page_cgroup.h | 6 ++++++
> scripts/tags.sh | 8 ++++++++
> 2 files changed, 14 insertions(+)
>
> diff --git a/include/linux/page_cgroup.h b/include/linux/page_cgroup.h
> index 777a524..9c60b77 100644
> --- a/include/linux/page_cgroup.h
> +++ b/include/linux/page_cgroup.h
> @@ -44,6 +44,12 @@ static inline void __init page_cgroup_init(void)
> struct page_cgroup *lookup_page_cgroup(struct page *page);
> struct page *lookup_cgroup_page(struct page_cgroup *pc);
>
> +/*
> + * Note, whenever you add a *PCGFLAG operation here, please add a
> + * regular expression replacement pattern in scripts/tags.sh
> + * to inform our friendly and smart tags generator.
> + */
> +
> #define TESTPCGFLAG(uname, lname) \
Cgroup hackers - OK to add the above comment? It does not look like new
macros are being defined here on a weekly basis...
> static inline int PageCgroup##uname(struct page_cgroup *pc) \
> { return test_bit(PCG_##lname, &pc->flags); }
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index 58c4559..c0d52d1 100755
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -171,12 +171,16 @@ exuberant()
> --regex-c++='/PAGEFLAG\(([^,)]*).*/ClearPage\1/' \
> --regex-c++='/TESTSETFLAG\(([^,)]*).*/TestSetPage\1/' \
> --regex-c++='/TESTPAGEFLAG\(([^,)]*).*/Page\1/' \
> + --regex-c++='/TESTPCGFLAG\(([^,)]*).*/PageCgroup\1/' \
> --regex-c++='/SETPAGEFLAG\(([^,)]*).*/SetPage\1/' \
> --regex-c++='/__SETPAGEFLAG\(([^,)]*).*/__SetPage\1/' \
> + --regex-c++='/SETPCGFLAG\(([^,)]*).*/SetPageCgroup\1/' \
> --regex-c++='/TESTCLEARFLAG\(([^,)]*).*/TestClearPage\1/' \
> --regex-c++='/__TESTCLEARFLAG\(([^,)]*).*/TestClearPage\1/' \
> + --regex-c++='/TESTCLEARPCGFLAG\(([^,)]*).*/TestClearPageCgroup\1/' \
> --regex-c++='/CLEARPAGEFLAG\(([^,)]*).*/ClearPage\1/' \
> --regex-c++='/__CLEARPAGEFLAG\(([^,)]*).*/__ClearPage\1/' \
> + --regex-c++='/CLEARPCGFLAG\(([^,)]*).*/ClearPageCgroup\1/' \
> --regex-c++='/__PAGEFLAG\(([^,)]*).*/__SetPage\1/' \
> --regex-c++='/__PAGEFLAG\(([^,)]*).*/__ClearPage\1/' \
> --regex-c++='/PAGEFLAG_FALSE\(([^,)]*).*/Page\1/' \
Please do not interleave the new defines with the <linux/page-flags.h>
defines.
Michal
> @@ -229,12 +233,16 @@ emacs()
> --regex='/PAGEFLAG(\([^,)]*\).*/ClearPage\1/' \
> --regex='/TESTSETFLAG(\([^,)]*\).*/TestSetPage\1/' \
> --regex='/TESTPAGEFLAG(\([^,)]*\).*/Page\1/' \
> + --regex='/TESTPCGFLAG\(([^,)]*).*/PageCgroup\1/' \
> --regex='/SETPAGEFLAG(\([^,)]*\).*/SetPage\1/' \
> --regex='/__SETPAGEFLAG(\([^,)]*\).*/__SetPage\1/' \
> + --regex='/SETPCGFLAG\(([^,)]*).*/SetPageCgroup\1/' \
> --regex='/TESTCLEARFLAG(\([^,)]*\).*/TestClearPage\1/' \
> --regex='/__TESTCLEARFLAG(\([^,)]*\).*/TestClearPage\1/' \
> + --regex='/TESTCLEARPCGFLAG\(([^,)]*).*/TestClearPageCgroup\1/' \
> --regex='/CLEARPAGEFLAG(\([^,)]*\).*/ClearPage\1/' \
> --regex='/__CLEARPAGEFLAG(\([^,)]*\).*/__ClearPage\1/' \
> + --regex='/CLEARPCGFLAG\(([^,)]*).*/ClearPageCgroup\1/' \
> --regex='/__PAGEFLAG(\([^,)]*\).*/__SetPage\1/' \
> --regex='/__PAGEFLAG(\([^,)]*\).*/__ClearPage\1/' \
> --regex='/PAGEFLAG_FALSE(\([^,)]*\).*/Page\1/' \
>
next prev parent reply other threads:[~2014-04-16 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 12:58 [PATCH] scripts/tags.sh: add regular expression replacement pattern for memcg Jianyu Zhan
2014-04-16 21:24 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-13 13:26 Jianyu Zhan
2014-05-14 11:50 ` Michal Marek
2014-04-17 13:37 Jianyu Zhan
2014-04-10 8:11 Jianyu Zhan
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=534EF4F6.8000900@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=nasa4836@gmail.com \
--cc=tkhai@yandex.ru \
/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.