From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: Akhilesh Kumar <akhilesh.lxr@gmail.com>
Cc: "david@fromorbit.com" <david@fromorbit.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mgorman@suse.de" <mgorman@suse.de>,
"riel@redhat.com" <riel@redhat.com>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ashmem_shrink with long term stable kernel [3.0.36]
Date: Tue, 26 Jun 2012 12:51:26 +0400 [thread overview]
Message-ID: <4FE9780E.5050403@openvz.org> (raw)
In-Reply-To: <CADArhcAxf3g=SLgDaJJMpzNpL_X7fbVbL1jzBYiyjPQFxXLYTA@mail.gmail.com>
Akhilesh Kumar wrote:
> Hi All,
>
> During mm performance testing sometimes we observed below kernel messages
>
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2133936901
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2139256767
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2079333971
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2096156269
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-20658392
>
> After debugging is we fount below patch mm/vmscan
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=635697c663f38106063d5659f0cf2e45afcd4bb5
> Since patch fix critical issue and same is not integrated with long term stable kernel (3.0.36)
> and we are using below patch with long term stable kernel (3.0.36) is there any side effects ?
Nothing special, your patch should work fine.
> @@ -248,10 +248,12 @@ unsigned long shrink_slab(struct shrink_control *shrink,
>
> list_for_each_entry(shrinker, &shrinker_list, list) {
> unsigned long long delta;
> - unsigned long total_scan;
> - unsigned long max_pass;
> + long total_scan;
> + long max_pass;
>
> max_pass = do_shrinker_shrink(shrinker, shrink, 0);
> + if (max_pass <= 0)
> + continue;
> delta = (4 * nr_pages_scanned) / shrinker->seeks;
> delta *= max_pass;
> do_div(delta, lru_pages + 1);
> --
> Please review and share ur comments.
> Thanks,
> Akhilesh
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: Akhilesh Kumar <akhilesh.lxr@gmail.com>
Cc: "david@fromorbit.com" <david@fromorbit.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mgorman@suse.de" <mgorman@suse.de>,
"riel@redhat.com" <riel@redhat.com>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ashmem_shrink with long term stable kernel [3.0.36]
Date: Tue, 26 Jun 2012 12:51:26 +0400 [thread overview]
Message-ID: <4FE9780E.5050403@openvz.org> (raw)
In-Reply-To: <CADArhcAxf3g=SLgDaJJMpzNpL_X7fbVbL1jzBYiyjPQFxXLYTA@mail.gmail.com>
Akhilesh Kumar wrote:
> Hi All,
>
> During mm performance testing sometimes we observed below kernel messages
>
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2133936901
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2139256767
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2079333971
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-2096156269
> shrink_slab: ashmem_shrink+0x0/0x114 negative objects to delete nr=-20658392
>
> After debugging is we fount below patch mm/vmscan
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=635697c663f38106063d5659f0cf2e45afcd4bb5
> Since patch fix critical issue and same is not integrated with long term stable kernel (3.0.36)
> and we are using below patch with long term stable kernel (3.0.36) is there any side effects ?
Nothing special, your patch should work fine.
> @@ -248,10 +248,12 @@ unsigned long shrink_slab(struct shrink_control *shrink,
>
> list_for_each_entry(shrinker, &shrinker_list, list) {
> unsigned long long delta;
> - unsigned long total_scan;
> - unsigned long max_pass;
> + long total_scan;
> + long max_pass;
>
> max_pass = do_shrinker_shrink(shrinker, shrink, 0);
> + if (max_pass <= 0)
> + continue;
> delta = (4 * nr_pages_scanned) / shrinker->seeks;
> delta *= max_pass;
> do_div(delta, lru_pages + 1);
> --
> Please review and share ur comments.
> Thanks,
> Akhilesh
next prev parent reply other threads:[~2012-06-26 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 8:03 ashmem_shrink with long term stable kernel [3.0.36] Akhilesh Kumar
2012-06-26 8:51 ` Konstantin Khlebnikov [this message]
2012-06-26 8:51 ` Konstantin Khlebnikov
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=4FE9780E.5050403@openvz.org \
--to=khlebnikov@openvz.org \
--cc=akhilesh.lxr@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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 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.