Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757272Ab0KJWYR (ORCPT ); Wed, 10 Nov 2010 17:24:17 -0500 Received: from ms01.sssup.it ([193.205.80.99]:45370 "EHLO sssup.it" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757208Ab0KJWYQ (ORCPT ); Wed, 10 Nov 2010 17:24:16 -0500 Subject: Re: [RFC][PATCH 02/22] sched: add extended scheduling interface From: Raistlin To: Peter Zijlstra Cc: Ingo Molnar , Thomas Gleixner , Steven Rostedt , Chris Friesen , oleg@redhat.com, Frederic Weisbecker , Darren Hart , Johan Eker , "p.faure" , linux-kernel , Claudio Scordino , michael trimarchi , Fabio Checconi , Tommaso Cucinotta , Juri Lelli , Nicola Manica , Luca Abeni , Dhaval Giani , Harald Gustafsson , paulmck In-Reply-To: <1289410114.2084.23.camel@laptop> References: <1288333128.8661.137.camel@Palantir> <1288333622.8661.141.camel@Palantir> <1289410114.2084.23.camel@laptop> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-ZzycIuNKBkgH0kTNLgxF" Date: Wed, 10 Nov 2010 23:24:05 +0100 Message-ID: <1289427845.13577.292.camel@Palantir> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2159 Lines: 62 --=-ZzycIuNKBkgH0kTNLgxF Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2010-11-10 at 18:28 +0100, Peter Zijlstra wrote: > On Fri, 2010-10-29 at 08:27 +0200, Raistlin wrote: > > +struct sched_param_ex { > > + int sched_priority; > > + struct timespec sched_runtime; > > + struct timespec sched_deadline; > > + struct timespec sched_period; > > + unsigned int sched_flags; > > + > > + struct timespec curr_runtime; > > + struct timespec used_runtime; > > + struct timespec curr_deadline; > > +};=20 > > I would suggest we add at least one more field so we can implement the > stochastic model from UNC, sched_runtime_dev or sched_runtime_var or > somesuch. >=20 Moreover, I really think that the capability of reporting back current and used runtime (and deadline) would be very useful for implementing more complex (and effective) scheduling behaviour in userspace... And in fact I added them here. Something I was not so sure, and thus about what I wanted your opinion, was if I should put these things here --so that they are retrievable by a sched_getparam[_ex, 2], or either add yet another syscall specific for that? Thoughts? Thanks, Dario --=20 <> (Raistlin Majere) ---------------------------------------------------------------------- Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy) http://blog.linux.it/raistlin / raistlin@ekiga.net / dario.faggioli@jabber.org --=-ZzycIuNKBkgH0kTNLgxF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAkzbG4UACgkQk4XaBE3IOsQzcACfSdRsoXf+W/J1tOqFCA/fGyCL L5cAnjXyBDXUlXczN1EzCi2pyL8zjkN5 =yE+K -----END PGP SIGNATURE----- --=-ZzycIuNKBkgH0kTNLgxF-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/