public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	Nick Piggin <npiggin@suse.de>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Rationalize sys_sched_rr_get_interval()
Date: Fri, 12 Oct 2007 08:59:17 +0200	[thread overview]
Message-ID: <20071012065917.GC3057@elte.hu> (raw)
In-Reply-To: <470EA277.7090107@bigpond.net.au>


* Peter Williams <pwil3058@bigpond.net.au> wrote:

> > I had also considered introducing smth like 
> > sched_class::task_timeslice() but decided it was not worth it.
> 
> The reason I was going that route was for modularity (which helps when 
> adding plugsched patches).  I'll submit a revised patch for 
> consideration.

no strong feelings - since this isnt a performance-sensitive codepath we 
could certainly abstract it a bit more if it's convenient for 
hackability. Depends on how the patch looks like and how much code 
increase there is - but i'd not expect it to be anything controversial.

	Ingo

      parent reply	other threads:[~2007-10-12  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  0:37 [PATCH] sched: Rationalize sys_sched_rr_get_interval() Peter Williams
2007-10-11  6:59 ` Ingo Molnar
2007-10-11  7:44   ` Dmitry Adamushko
2007-10-11 22:23     ` Peter Williams
2007-10-12  6:49       ` Jarek Poplawski
2007-10-13  1:29         ` Peter Williams
2007-10-15 11:11           ` Jarek Poplawski
2007-10-16  1:16             ` Peter Williams
2007-10-16  9:42               ` Jarek Poplawski
2007-10-17  0:23                 ` Peter Williams
2007-10-12  6:59       ` Ingo Molnar [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=20071012065917.GC3057@elte.hu \
    --to=mingo@elte.hu \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=pwil3058@bigpond.net.au \
    --cc=suresh.b.siddha@intel.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