mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Sergey Oboguev <oboguev.public@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, khalid.aziz@oracle.com
Subject: Re: [PATCH RFC] sched: deferred set priority (dprio)
Date: Sun, 03 Aug 2014 11:56:16 +0200	[thread overview]
Message-ID: <1407059776.5156.108.camel@marge.simpson.net> (raw)
In-Reply-To: <CA+80gGaohO-RaG0_tWZJEFzisrrBpgfiw-mxMrTfSK0N=k7gQA@mail.gmail.com>

On Sat, 2014-08-02 at 17:43 -0700, Sergey Oboguev wrote:

> When reasoning about concurrency management it may be helpful to keep in mind
> the fundamental perspective that the problem space and solution space in this
> area are fragmented -- just as your message exemplifies as well, but it also
> applies across the board to all other solution techniques. There is no
> all-unifying solution that works in all use cases and for all purposes.

I'm just not seeing the beauty in your patch.  Ignoring SCHED_NORMAL
where priority escalation does not work as preemption proofing, for
realtime classes, what I see is a programmer using a mechanism designed
to initiate preemption arming his tasks with countermeasures to the very
thing he initiates.  Deferred preempt seems to be what you want, but you
invented something very different.

As noted though, you don't have to convince me.  The thing to do is chop
your patch up into a nice reviewable series, and submit it.

-Mike


  reply	other threads:[~2014-08-03  9:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 19:45 Sergey Oboguev
2014-07-25 20:12 ` Andy Lutomirski
2014-07-26  7:56   ` Sergey Oboguev
2014-07-26  8:58 ` Mike Galbraith
2014-07-26 18:30   ` Sergey Oboguev
2014-07-27  4:02     ` Mike Galbraith
2014-07-27  9:09       ` Sergey Oboguev
2014-07-27 10:29         ` Mike Galbraith
2014-07-28  1:19 ` Andi Kleen
2014-07-28  4:16   ` Sergey Oboguev
2014-07-28  7:24   ` Mike Galbraith
2014-08-03  0:43     ` Sergey Oboguev
2014-08-03  9:56       ` Mike Galbraith [this message]
2014-08-05 23:28         ` Sergey Oboguev
2014-08-06  5:41           ` Mike Galbraith
2014-08-06  7:42             ` Mike Galbraith
2014-08-07  1:26             ` Sergey Oboguev
2014-08-07  9:03               ` Mike Galbraith
2014-08-08 20:11                 ` Sergey Oboguev
2014-08-09 13:04                   ` Mike Galbraith
2014-08-09 18:04                     ` Andi Kleen
2014-08-10  3:13                       ` Mike Galbraith
2014-08-10  3:41                         ` Mike Galbraith
2014-08-13 23:52                     ` Sergey Oboguev
2014-08-09  8:38                 ` Sergey Oboguev
2014-08-09 14:13                   ` Mike Galbraith
2014-08-03 17:30       ` Andi Kleen
2014-08-05 23:13         ` Sergey Oboguev
2014-07-30 13:02 ` Pavel Machek
2014-08-03  0:47   ` Sergey Oboguev
2014-08-03  8:30     ` Pavel Machek
2014-08-05 23:03       ` Sergey Oboguev
  -- strict thread matches above, loose matches on Subject: below --
2014-07-21 12:33 Sergey Oboguev
2014-07-21 18:14 ` Thomas Gleixner

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=1407059776.5156.108.camel@marge.simpson.net \
    --to=umgwanakikbuti@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=khalid.aziz@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oboguev.public@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

all inboxes | Powered by JetHome®