From: Michal Hocko <mhocko@kernel.org>
To: Vladimir Davydov <vdavydov@virtuozzo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] oom: make oom_reaper_list single linked
Date: Tue, 1 Mar 2016 15:01:34 +0100 [thread overview]
Message-ID: <20160301140133.GG9461@dhcp22.suse.cz> (raw)
In-Reply-To: <1456824500-30661-1-git-send-email-vdavydov@virtuozzo.com>
On Tue 01-03-16 12:28:20, Vladimir Davydov wrote:
> Entries are only added/removed from oom_reaper_list at head so we can
> use a single linked list and hence save a word in task_struct.
There was a larger hole when I've checked the last time but why not.
> Signed-off-by: Vladimir Davydov <vdavydov@virtuozzo.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!
> ---
> include/linux/sched.h | 2 +-
> mm/oom_kill.c | 15 +++++++--------
> 2 files changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 2118e963fba7..7b76e65595c3 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -1853,7 +1853,7 @@ struct task_struct {
> #endif
> int pagefault_disabled;
> #ifdef CONFIG_MMU
> - struct list_head oom_reaper_list;
> + struct task_struct *oom_reaper_list;
> #endif
> /* CPU-specific state of this task */
> struct thread_struct thread;
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 5d5eca9d6737..1a91d9a26bc9 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -423,7 +423,7 @@ bool oom_killer_disabled __read_mostly;
> */
> static struct task_struct *oom_reaper_th;
> static DECLARE_WAIT_QUEUE_HEAD(oom_reaper_wait);
> -static LIST_HEAD(oom_reaper_list);
> +static struct task_struct *oom_reaper_list;
> static DEFINE_SPINLOCK(oom_reaper_lock);
>
>
> @@ -530,13 +530,11 @@ static int oom_reaper(void *unused)
> while (true) {
> struct task_struct *tsk = NULL;
>
> - wait_event_freezable(oom_reaper_wait,
> - (!list_empty(&oom_reaper_list)));
> + wait_event_freezable(oom_reaper_wait, oom_reaper_list != NULL);
> spin_lock(&oom_reaper_lock);
> - if (!list_empty(&oom_reaper_list)) {
> - tsk = list_first_entry(&oom_reaper_list,
> - struct task_struct, oom_reaper_list);
> - list_del(&tsk->oom_reaper_list);
> + if (oom_reaper_list != NULL) {
> + tsk = oom_reaper_list;
> + oom_reaper_list = tsk->oom_reaper_list;
> }
> spin_unlock(&oom_reaper_lock);
>
> @@ -555,7 +553,8 @@ static void wake_oom_reaper(struct task_struct *tsk)
> get_task_struct(tsk);
>
> spin_lock(&oom_reaper_lock);
> - list_add(&tsk->oom_reaper_list, &oom_reaper_list);
> + tsk->oom_reaper_list = oom_reaper_list;
> + oom_reaper_list = tsk;
> spin_unlock(&oom_reaper_lock);
> wake_up(&oom_reaper_wait);
> }
> --
> 2.1.4
--
Michal Hocko
SUSE Labs
--
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>
prev parent reply other threads:[~2016-03-01 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 9:28 [PATCH -mm] oom: make oom_reaper_list single linked Vladimir Davydov
2016-03-01 14:01 ` Michal Hocko [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=20160301140133.GG9461@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=vdavydov@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).