From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
LKML <linux-kernel@vger.kernel.org>,
Paul Menage <menage@google.com>,
David Rientjes <rientjes@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 1/4] oom: move oom_adj to signal_struct
Date: Wed, 5 Aug 2009 15:47:31 +0900 (JST) [thread overview]
Message-ID: <20090805153157.5BBF.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090805152956.faf52a5a.minchan.kim@barrios-desktop>
> > > What do you think about this approach ?
> >
> > I can ack this. but please re-initialize oom_scale_down at fork and
> > exec time.
> > currently oom_scale_down makes too big affect.
>
>
> Thanks for carefult review.
> In fact, I didn't care of it
> since it just is RFC for making sure my idea. :)
ok, I see.
> > and, May I ask which you hate my approach?
>
> Not at all. I never hate your approach.
> This problem resulted form David's original patch.
> I thought if we will fix live lock with different approach, we can remove much pain.
I also think your approach is enough acceptable.
ok, Let's wait one night and to hear other developer's opinion.
We can choice more lkml preferred approach :)
--
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:[~2009-08-05 6:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 10:25 [PATCH for 2.6.31 0/4] fix oom_adj regression v2 KOSAKI Motohiro
2009-08-04 10:25 ` [PATCH 1/4] oom: move oom_adj to signal_struct KOSAKI Motohiro
2009-08-05 0:45 ` Minchan Kim
2009-08-05 2:29 ` KOSAKI Motohiro
2009-08-05 2:40 ` Minchan Kim
2009-08-05 2:51 ` KOSAKI Motohiro
2009-08-05 5:55 ` Minchan Kim
2009-08-05 6:03 ` KAMEZAWA Hiroyuki
2009-08-05 6:37 ` Minchan Kim
2009-08-05 6:53 ` KOSAKI Motohiro
2009-08-05 7:20 ` Minchan Kim
2009-08-05 6:55 ` KAMEZAWA Hiroyuki
2009-08-05 6:04 ` KOSAKI Motohiro
2009-08-05 6:29 ` Minchan Kim
2009-08-05 6:47 ` KOSAKI Motohiro [this message]
2009-08-06 1:34 ` Oleg Nesterov
2009-08-06 5:16 ` KOSAKI Motohiro
2009-08-04 10:26 ` [PATCH 2/4] oom: make oom_score to per-process value KOSAKI Motohiro
2009-08-04 10:27 ` [PATCH 3/4] oom: oom_kill doesn't kill vfork parent(or child) KOSAKI Motohiro
2009-08-04 10:28 ` [PATCH 4/4] oom: fix oom_adjust_write() input sanity check KOSAKI Motohiro
2009-08-05 23:33 ` Andrew Morton
2009-08-06 5:06 ` KOSAKI Motohiro
2009-08-05 23:39 ` [PATCH for 2.6.31 0/4] fix oom_adj regression v2 Andrew Morton
2009-08-06 5:13 ` KOSAKI Motohiro
2009-08-06 8:07 ` Minchan Kim
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=20090805153157.5BBF.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=minchan.kim@gmail.com \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
/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