From: Stephan Diestelhorst <sd386@cam.ac.uk>
To: John L Griffin <jlg@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Getting and setting SEDF scheduling parameters
Date: Thu, 12 Jan 2006 08:29:54 +0100 [thread overview]
Message-ID: <43C60572.3080803@cam.ac.uk> (raw)
In-Reply-To: <OF56748F8E.8A763F25-ON852570ED.0068B675-852570ED.006AC522@us.ibm.com>
John L Griffin wrote:
>This patch addresses three problems in the function sedf_adjdom():
>
>3) The code logic in this function is cryptic, and there is not much
>documentation on how the scheduling parameters should be used. The
>attached patch adds comments to the sedf_adjdom() function, and
>reorders/rewrites the logic of the SCHED_INFO_PUT handling to make the
>code more self-documenting.
>
>
I know, the main problem is, that there are quite a number of different
interpretations for some of the values, depending on the others. This
caused some cryptic code as you point out properly, which I wasn't
really happy with!
Stephan
>Note that this patch makes strong assumptions about how the scheduling
>parameters are used. So, I recommend someone take a really close look at
>my comments to make sure I've preserved the Xen team's intentions for how
>the SEDF scheduler works. :-)
>
>Signed-off-by: jlg@us.ibm.com
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
prev parent reply other threads:[~2006-01-12 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 19:26 [PATCH] Getting and setting SEDF scheduling parameters John L Griffin
2006-01-06 10:37 ` Keir Fraser
2006-01-09 20:42 ` John L Griffin
2006-01-12 7:45 ` Stephan Diestelhorst
2006-01-12 7:29 ` Stephan Diestelhorst [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=43C60572.3080803@cam.ac.uk \
--to=sd386@cam.ac.uk \
--cc=jlg@us.ibm.com \
--cc=xen-devel@lists.xensource.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.