From: Nikolay Borisov <kernel@kyup.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-mm@kvack.org, mgorman@suse.de,
Andrew Morton <akpm@linux-foundation.org>,
Marian Marinov <mm@1h.com>,
SiteGround Operations <operations@siteground.com>
Subject: Re: Making per-cpu lists draining dependant on a flag
Date: Tue, 13 Oct 2015 17:55:43 +0300 [thread overview]
Message-ID: <561D1B6F.8080509@kyup.com> (raw)
In-Reply-To: <20151013144335.GB31034@dhcp22.suse.cz>
On 10/13/2015 05:43 PM, Michal Hocko wrote:
> On Fri 09-10-15 14:00:31, Nikolay Borisov wrote:
>> Hello mm people,
>>
>>
>> I want to ask you the following question which stemmed from analysing
>> and chasing this particular deadlock:
>> http://permalink.gmane.org/gmane.linux.kernel/2056730
>>
>> To summarise it:
>>
>> For simplicity I will use the following nomenclature:
>> t1 - kworker/u96:0
>> t2 - kworker/u98:39
>> t3 - kworker/u98:7
>
> Could you be more specific about the trace of all three parties?
> I am not sure I am completely following your description. Thanks!
Hi,
Maybe you'd want to check this thread:
http://thread.gmane.org/gmane.linux.kernel/2056996
Essentially, in the beginning I thought the problem could be in the
memory manager but after discussing with Jan Kara I thought the problem
doesn't like in the memory manager.
>
--
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:[~2015-10-13 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 11:00 Making per-cpu lists draining dependant on a flag Nikolay Borisov
2015-10-13 14:43 ` Michal Hocko
2015-10-13 14:55 ` Nikolay Borisov [this message]
2015-10-14 8:37 ` Michal Hocko
2015-10-14 9:06 ` Nikolay Borisov
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=561D1B6F.8080509@kyup.com \
--to=kernel@kyup.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=mm@1h.com \
--cc=operations@siteground.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.