From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org,
Harmandeep Kaur <write.harmandeep@gmail.com>
Subject: Re: [PATCH] sched_credit: Remove cpu argument to __runq_insert()
Date: Mon, 2 Nov 2015 12:01:55 +0100 [thread overview]
Message-ID: <1446462115.3829.8.camel@citrix.com> (raw)
In-Reply-To: <5633B03F02000078000B0599@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1532 bytes --]
[Trimming the Cc list, and adding George, which I did not realize he
was not there!]
On Fri, 2015-10-30 at 11:00 -0600, Jan Beulich wrote:
> > > > On 30.10.15 at 17:33, <dario.faggioli@citrix.com> wrote:
> > Are you saying that we shouldn't make the change at all? Or that we
> > should make the change and also turn the BUG_ON() (the one that is
> > left
> > in place) into an ASSERT()? Or that we should not mark the function
> > as
> > 'inline'?
>
> No, I'm suggesting that instead of this change the BUG_ON() (or
> perhaps both and also others) should be converted to ASSERT().
>
I'm all in favour of turning these two (if both are staying) BUG_ON()s
in ASSERT()s.
What I especially don't like of the function right now, is that by
looking at the prototype, and at least at some of the call sites, it
feels like it is possible to insert a vCPU v in the runqueue of an
arbitrary pCPU, while that must always happens in v->processor's
runqueue. That is why I'd like to be able to remove that cpu argument.
Perhaps avoiding inlining can really be considered? Looking at history,
the function was shorter and called less times when originally
developed and marked as such. I'm not sure that's still a good thing...
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:[~2015-11-02 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 15:09 [PATCH] sched_credit: Remove cpu argument to __runq_insert() Harmandeep Kaur
2015-10-30 16:25 ` Jan Beulich
2015-10-30 16:33 ` Dario Faggioli
2015-10-30 17:00 ` Jan Beulich
2015-11-02 11:01 ` Dario Faggioli [this message]
2015-11-03 10:16 ` George Dunlap
2015-11-03 12:38 ` Jan Beulich
2015-11-03 21:22 ` Dario Faggioli
2015-10-30 16:46 ` Dario Faggioli
2015-10-30 16:50 ` Harmandeep Kaur
2015-10-30 17:01 ` Dario Faggioli
2015-11-02 12:36 ` Wei Liu
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=1446462115.3829.8.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=write.harmandeep@gmail.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 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.