From: "Doug Smythies" <dsmythies@telus.net>
To: 'Joonsoo Kim' <iamjoonsoo.kim@lge.com>
Cc: 'Vladimir Davydov' <vdavydov.dev@gmail.com>,
'Johannes Weiner' <hannes@cmpxchg.org>,
'Andrew Morton' <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
'Doug Smythies' <dsmythies@telus.net>
Subject: RE: [Bug 172981] New: [bisected] SLAB: extreme load averages and over 2000 kworker threads
Date: Fri, 7 Oct 2016 08:55:23 -0700 [thread overview]
Message-ID: <004d01d220b3$38a1ac40$a9e504c0$@net> (raw)
In-Reply-To:
On 2016.10.06 09:02 Doug Smythies wrote:
> On 2016.10.05 23:35 Joonsoo Kim wrote:
>> On Wed, Oct 05, 2016 at 10:04:27PM -0700, Doug Smythies wrote:
>>> On 2016.09.30 12:59 Vladimir Davydov wrote:
>>>
>>>> Yeah, you're right. We'd better do something about this
>>>> synchronize_sched(). I think moving it out of the slab_mutex and calling
>>>> it once for all caches in memcg_deactivate_kmem_caches() would resolve
>>>> the issue. I'll post the patches tomorrow.
>>>
>>> Would someone please be kind enough to send me the patch set?
>>>
>>> I didn't get them, and would like to test them.
>>> I have searched and searched and did manage to find:
>>> "[PATCH 2/2] slub: move synchronize_sched out of slab_mutex on shrink"
>>> And a thread about a patch 1 of 2:
>>> "Re: [PATCH 1/2] mm: memcontrol: use special workqueue for creating per-memcg caches"
>>> Where I see me as "reported by", but I guess "reported by" people don't get the e-mails.
>>> I haven't found PATCH 0/2, nor do I know if what I did find is current.
>>
>> I think that what you find is correct one. It has no cover-letter so
>> there is no [PATCH 0/2]. Anyway, to clarify, I add links to these
>> patches.
>>
>> https://patchwork.kernel.org/patch/9361853
>> https://patchwork.kernel.org/patch/9359271
>>
>> It would be very helpful if you test these patches.
>
> Yes, as best as I am able to test, the 2 patch set
> solves both this SLAB and the other SLUB bug reports.
I tested the patch from the other thread on top of these two,
And things continued to work fine. The additional patch
does seems a little faster under some of my hammering conditions.
Reference:
https://marc.info/?l=linux-kernel&m=147573486705407&w=2
--
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:[~2016-10-07 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-172981-27@https.bugzilla.kernel.org/>
2016-09-27 18:10 ` [Bug 172981] New: [bisected] SLAB: extreme load averages and over 2000 kworker threads Andrew Morton
2016-09-28 2:03 ` Johannes Weiner
2016-09-28 8:09 ` Vladimir Davydov
2016-09-29 2:00 ` Joonsoo Kim
2016-09-29 13:45 ` Vladimir Davydov
2016-09-30 8:19 ` Joonsoo Kim
2016-09-30 19:58 ` Vladimir Davydov
2016-10-06 5:04 ` Doug Smythies
2016-10-06 6:35 ` Joonsoo Kim
2016-10-06 16:02 ` Doug Smythies
2016-10-07 15:55 ` Doug Smythies [this message]
2016-09-28 3:13 ` Doug Smythies
2016-09-28 5:18 ` Joonsoo Kim
2016-09-28 6:20 ` Joonsoo Kim
2016-09-28 15:22 ` Doug Smythies
2016-09-29 1:50 ` Joonsoo 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='004d01d220b3$38a1ac40$a9e504c0$@net' \
--to=dsmythies@telus.net \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.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).