From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>,
xen-devel@lists.xenproject.org,
George Dunlap <george.dunlap@citrix.com>
Subject: Re: [PATCH] xen: sched: get rid of static private schedulers' structures
Date: Tue, 9 Feb 2016 13:25:34 +0100 [thread overview]
Message-ID: <1455020734.3148.67.camel@citrix.com> (raw)
In-Reply-To: <56B9DB1D02000078000CFFCA@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1610 bytes --]
On Tue, 2016-02-09 at 04:27 -0700, Jan Beulich wrote:
> > > > On 08.02.16 at 14:19, <dario.faggioli@citrix.com> wrote:
> > @@ -1995,13 +1996,11 @@ static void csched_tick_resume(const struct
> > scheduler *ops, unsigned int cpu)
> > - now % MICROSECS(prv->tick_period_us) );
> > }
> >
> > -static struct csched_private _csched_priv;
> > -
> > static const struct scheduler sched_credit_def = {
> > .name = "SMP Credit Scheduler",
> > .opt_name = "credit",
> > .sched_id = XEN_SCHEDULER_CREDIT,
> > - .sched_data = &_csched_priv,
> > + .sched_data = NULL,
>
> You're maintainer of this code, so you know whether you really
> want these NULL initializers, but the look pretty pointless to me.
>
Yes, I've also been unsure about what to do here.
The reason why I put them there is that, when looking at the code, it
is important to be able to quickly get the idea of where sched_data
points, at any given time. Therefore, being a little bit more verbose
than necessary would be, in this case, actually helpful.
Anyway, this is not a super strong opinion, so I can be talked into
getting rid of them, if others think we better don't have them too.
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-09 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 13:19 [PATCH] xen: sched: get rid of static private schedulers' structures Dario Faggioli
2016-02-09 11:27 ` Jan Beulich
2016-02-09 12:25 ` Dario Faggioli [this message]
2016-02-23 12:29 ` George Dunlap
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=1455020734.3148.67.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=george.dunlap@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).