Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757335Ab0KJWpt (ORCPT ); Wed, 10 Nov 2010 17:45:49 -0500 Received: from ms01.sssup.it ([193.205.80.99]:40605 "EHLO sssup.it" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757010Ab0KJWps (ORCPT ); Wed, 10 Nov 2010 17:45:48 -0500 Subject: Re: [RFC][PATCH 02/22] sched: add extended scheduling interface From: Raistlin To: Dhaval Giani Cc: Peter Zijlstra , 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 , Harald Gustafsson , paulmck In-Reply-To: References: <1288333128.8661.137.camel@Palantir> <1288333622.8661.141.camel@Palantir> <20101110160004.GA9092@gondor.retis> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-tJ3lVUplMNasOE5oX8Yf" Date: Wed, 10 Nov 2010 23:45:35 +0100 Message-ID: <1289429135.13577.303.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: 2035 Lines: 63 --=-tJ3lVUplMNasOE5oX8Yf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2010-11-10 at 17:12 +0100, Dhaval Giani wrote: > >> + * @curr_runtime task's currently available runtime > >> + * @used_runtime task's totally used runtime > >> + * @curr_deadline task's current absolute deadline > >> + * > >> + * Given this task model, there are a multiplicity of scheduling algo= rithms > >> + * and policies, that can be used to ensure all the tasks will make t= heir > >> + * timing constraints. > >> + */ > >> +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 > Can we expose soem of these details via schedstats as opposed to a syscal= l? >=20 Actually, good point... schedstats seems very reasonable to me... What do the others think? 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 --=-tJ3lVUplMNasOE5oX8Yf 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) iEYEABECAAYFAkzbII8ACgkQk4XaBE3IOsTVRQCglhkXiMchvjHxKvSQss3O/ML/ SZoAmwRI8kRMSvZEnOYYw2C6m8j6nxuK =O0I2 -----END PGP SIGNATURE----- --=-tJ3lVUplMNasOE5oX8Yf-- -- 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/