linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: HeeSub Shin <heesub@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Heesub Shin <heesub.shin@samsung.com>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, mgorman@suse.de, riel@redhat.com,
	kyungmin.park@samsung.com, d.j.shin@samsung.com,
	sunae.seo@samsung.com
Subject: Re: [PATCH] mm: vmscan: remove redundant querying to shrinker
Date: Sat, 15 Jun 2013 03:13:26 +0900	[thread overview]
Message-ID: <CALSv+Dht=1ghRmiXdLwkFcXgRTwV=erSeoXc2AEh7+8XmHh1xQ@mail.gmail.com> (raw)
In-Reply-To: <20130614111034.GA306@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

Hello,

On Fri, Jun 14, 2013 at 8:10 PM, Minchan Kim <minchan@kernel.org> wrote:

>
> Hello,
>
> On Fri, Jun 14, 2013 at 07:07:51PM +0900, Heesub Shin wrote:
> > shrink_slab() queries each slab cache to get the number of
> > elements in it. In most cases such queries are cheap but,
> > on some caches. For example, Android low-memory-killer,
> > which is operates as a slab shrinker, does relatively
> > long calculation once invoked and it is quite expensive.
>
> LMK as shrinker is really bad, which everybody didn't want
> when we reviewed it a few years ago so that's a one of reason
> LMK couldn't be promoted to mainline yet. So your motivation is
> already not atrractive. ;-)
>
> >
> > This patch removes redundant queries to shrinker function
> > in the loop of shrink batch.
>
> I didn't review the patch and others don't want it, I guess.
> Because slab shrink is under construction and many patches were
> already merged into mmtom. Please look at latest mmotm tree.
>
>         git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git


>
> If you concern is still in there and it's really big concern of MM
> we should take care, NOT LMK, plese, resend it.
>
>
I've noticed that there are huge changes there in the recent mmotm and you
guys already settled the issue of my concern. I usually keep track changes
in recent mm-tree, but this time I didn't. My bad :-)

Many thanks for your comments!

--
Heesub


> Thanks.
>
> --
> Kind regards,
> Minchan Kim
>
> --
> 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>
>

[-- Attachment #2: Type: text/html, Size: 2920 bytes --]

  reply	other threads:[~2013-06-14 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 10:07 Heesub Shin
2013-06-14 11:10 ` Minchan Kim
2013-06-14 18:13   ` HeeSub Shin [this message]
2013-06-14 23:04     ` Andrew Morton
2013-06-15  0:49       ` Kyungmin Park
2013-06-15  6:47       ` Minchan Kim
2013-06-15  7:09 ` Minchan Kim
2013-06-17  0:08 ` Dave Chinner
2013-06-17  7:54   ` Heesub Shin

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='CALSv+Dht=1ghRmiXdLwkFcXgRTwV=erSeoXc2AEh7+8XmHh1xQ@mail.gmail.com' \
    --to=heesub@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=d.j.shin@samsung.com \
    --cc=heesub.shin@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=riel@redhat.com \
    --cc=sunae.seo@samsung.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