From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: MinChan Kim <minchan.kim@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com, Rik van Riel <riel@redhat.com>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
akpm@linux-foundation.org,
Takenori Nagano <t-nagano@ah.jp.nec.com>
Subject: Re: [RFC][PATCH] prevent incorrect oom under split_lru
Date: Wed, 25 Jun 2008 16:29:10 +0900 [thread overview]
Message-ID: <20080625161753.D848.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <28c262360806242358q348e18a4vb9c48b4b853b0384@mail.gmail.com>
> > But if such emergency happen in embedded system, application can't be
> > executed for some time.
> > I am not sure how long time it take.
> > But In some application, schedule period is very important than memory
> > reclaim latency.
> >
> > Now, In your patch, when such emergency happen, it continue to reclaim
> > page until it will scan entire page of lru list.
> > It
>
> with my mistake, I omit following message. :(
>
> So, we need cut-off mechanism to reduce application latency.
> So In my opinion, If we modify some code of Takenori's patch, we can
> apply his idea to prevent latency probelm.
Yup.
Agreed with latency is as important as throughput.
if anyone explain that patch have reduce some latency and
no throughput degression by benchmark result,
I have no objection, Of cource.
Can you post any performance result?
--
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:[~2008-06-25 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 8:31 KOSAKI Motohiro
2008-06-24 13:28 ` Rik van Riel
2008-06-25 5:59 ` MinChan Kim
2008-06-25 6:08 ` KOSAKI Motohiro
2008-06-25 6:56 ` MinChan Kim
2008-06-25 6:58 ` MinChan Kim
2008-06-25 7:29 ` KOSAKI Motohiro [this message]
2008-06-25 7:37 ` MinChan Kim
2008-06-25 12:11 ` Peter Zijlstra
2008-06-25 13:05 ` MinChan Kim
2008-06-26 1:49 ` Takenori Nagano
2008-06-26 4:37 ` MinChan Kim
2008-06-26 5:24 ` Takenori Nagano
2008-06-26 6:37 ` MinChan Kim
2008-06-26 8:05 ` Takenori Nagano
2008-06-26 0:36 ` KOSAKI Motohiro
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=20080625161753.D848.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.com \
--cc=t-nagano@ah.jp.nec.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