From: Kirill Tkhai <tkhai@yandex.ru>
To: Oleg Nesterov <oleg@redhat.com>, Kirill Tkhai <ktkhai@odin.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Michal Hocko <mhocko@suse.cz>, Rik van Riel <riel@redhat.com>,
Ionut Alexa <ionut.m.alexa@gmail.com>,
Peter Hurley <peter@hurleysoftware.com>
Subject: Re: [PATCH RFC 00/13] Reduction globality of tasklist_lock
Date: Fri, 29 May 2015 19:23:20 +0300 [thread overview]
Message-ID: <147161432916600@web19o.yandex.ru> (raw)
In-Reply-To: <635991432718342@web2o.yandex.ru>
27.05.2015, 12:30, "Kirill Tkhai" <tkhai@yandex.ru>:
> Hi, Oleg,
>
> 26.05.2015, 22:44, "Oleg Nesterov" <oleg@redhat.com>:
>> On 05/25, Kirill Tkhai wrote:
>>> It's like gone BKL,
>> Yes...
>>
>> Kirill. I just want to let you know that I am not going to ignore
>> this series. I'll try very much to review it this week.
>>
>> But I have to admit this scares me ;) and I don't feel this all
>> is right. We will see.
>
> Nice to hear. I'll wait for your commentaries.
> A couple of words how this all was tested.
>
> The strace test was endless kernel compilation using standard or
> straced gcc/make (CC="strace -o /dev/null gcc" ) and periodical
> killing gcc, make or strace. No problems were observed. If there
> is an idea of a test, which is mostly for threads, I'll be happy
> to hear it.
I found some problems in the patchset and going to fix them. Please,
ignore it. I'll send new series next week.
Kirill
prev parent reply other threads:[~2015-05-29 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 17:43 [PATCH RFC 00/13] Reduction globality of tasklist_lock Kirill Tkhai
2015-05-26 19:42 ` Oleg Nesterov
2015-05-27 9:19 ` Kirill Tkhai
2015-05-29 16:23 ` Kirill Tkhai [this message]
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=147161432916600@web19o.yandex.ru \
--to=tkhai@yandex.ru \
--cc=akpm@linux-foundation.org \
--cc=ionut.m.alexa@gmail.com \
--cc=ktkhai@odin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox