All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
	Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen: make sure the node-affinity is always updated
Date: Fri, 13 Sep 2013 17:45:17 +0200	[thread overview]
Message-ID: <1379087117.6095.66.camel@Solace> (raw)
In-Reply-To: <1379076235.31009.74.camel@Abyss>


[-- Attachment #1.1: Type: text/plain, Size: 1261 bytes --]

On ven, 2013-09-13 at 14:43 +0200, Dario Faggioli wrote:
> On ven, 2013-09-13 at 11:45 +0100, George Dunlap wrote:
> > But that's a UI polish thing, rather than a bug fix, so is slightly
> > lower priority.
> > 
> Sure, but I was really concerned about making the interface a mess, even
> if that happens by fixing the bug.
> 
> I'll think about it a bit more, and see if I can come up with a
> different, less "surprising" solution from the UI standpoint in the next
> hours, ok?
> 
Ok, I did found a way to deal with this entirely in the (credit)
scheduler, without adding too many cpumask operations (well, I added a
cpumask_and() in _csched_cpu_pick(), but that's it).

I'll send it as a new patch, containing only the minimum required to fix
the bug, so to make backporting easier.

Jurgen, I'll bundle the cpupool hunk with a couple of other patches I've
got about cpupools changes I have in my queue and send a series in the
coming days.

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: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2013-09-13 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 15:57 [PATCH] xen: make sure the node-affinity is always updated Dario Faggioli
2013-09-13  4:31 ` Juergen Gross
2013-09-13  9:52 ` Dario Faggioli
2013-09-26  8:05   ` Jan Beulich
2013-09-13 10:45 ` George Dunlap
2013-09-13 12:43   ` Dario Faggioli
2013-09-13 15:45     ` Dario Faggioli [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=1379087117.6095.66.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=juergen.gross@ts.fujitsu.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.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.