From: Shuah Khan <shuahkhan@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] cleaning up kthread freezer hell, part 2
Date: Sat, 9 Jul 2016 06:44:44 -0600 [thread overview]
Message-ID: <CAKocOOPNLbXo8g3OwdG8zsZ7wJozRGjtn3T74hBz4TqWaha1DQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1607090819190.3236@hadrien>
On Sat, Jul 9, 2016 at 12:19 AM, Julia Lawall <julia.lawall@lip6.fr> wrote:
>
>
> On Sat, 9 Jul 2016, Rafael J. Wysocki wrote:
>
>> On Saturday, July 09, 2016 12:31:33 AM Jiri Kosina wrote:
>> > On last year's kernel summit, I've been talking about why I consider
>> > kthread freezer harmful and why it ultimately should be removed. LWN
>> > coverage of that session is here:
>> >
>> > https://lwn.net/Articles/662703/
>> >
>> > During the past year, I've invested a bit of a time into actually looking
>> > deeper into the dark corners of kernel sources to see how kthread freezer
>> > is used throughout the codebase, with the intent to ultimately fix all the
>> > buggy places. While doing that, I was petrified by two facts:
>> >
>> > - there are a *lot* of places where kthread freezer is used in a
>> > completely buggy (or useless) way
>> >
>> > - one of the obstacles fixing it are maintainers who actually don't
>> > understand the purpose of the kthread freezer (the usual pattern is that
>> > the main kthread loop has been copy/pasted from different code, which
>> > already used freezer, and so disease spreads)
>> >
>> > Therefore I'd propose a v2 of the last year's session; first summarizing
>> > the horrible experience I've done on this kthread freezer journey, and as
>> > a followup, try to (re-)explain the issue and the way I think it should be
>> > resolved.
>>
>> Yes, please.
>>
>> Let me know if/how I can help.
>
> Likewise.
>
Yes. Count me in to help out on this.
-- Shuah
>
>>
>> > The idea is to get as much coverage among high-profile maintainers as
>> > possible, in a hope that this will result in ultimate tree-wide cleanup of
>> > the current mess. That's why I propose this as a core topic rather than
>> > tech topic, although it might sound like a rather bordeline one.
>>
>> I guess that first needs to be "core" so it can become "tech" later when
>> everybody is on the same page in general.
>>
>> Thanks,
>> Rafael
>>
>> _______________________________________________
>> Ksummit-discuss mailing list
>> Ksummit-discuss@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>>
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2016-07-09 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 22:31 Jiri Kosina
2016-07-08 23:19 ` Rafael J. Wysocki
2016-07-09 6:19 ` Julia Lawall
2016-07-09 12:44 ` Shuah Khan [this message]
2016-07-10 23:55 ` Theodore Ts'o
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=CAKocOOPNLbXo8g3OwdG8zsZ7wJozRGjtn3T74hBz4TqWaha1DQ@mail.gmail.com \
--to=shuahkhan@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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