xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: xen-devel@lists.xenproject.org, jgross@suse.com
Subject: Re: [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update
Date: Fri, 02 Aug 2019 11:57:34 +0200	[thread overview]
Message-ID: <8558ac91c3b555619a9866a339e4db20817ef626.camel@suse.com> (raw)
In-Reply-To: <20190801160048.11031-1-jgross@suse.com>


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

On Thu, 2019-08-01 at 18:00 +0200, Juergen Gross wrote:
> 
> = Projects =
> 
> == Hypervisor == 
> 
> [...]
>
> *  Core aware scheduling (RFC v1)
>   -  Dario Faggioli
> 
> *  Core aware scheduling for credit2 (RFC v1)
>   -  Dario Faggioli
> 
So, in theory, my patches can be made work on top of yours. And if one
does not work core-scheduling, but just core-aware scheduling, can boot
with sched-gran=cpu ("disabling" core-scheduling from Juergen's
patches) and with credit2-group-sched=core ("enabling" only core-aware
scheduling, from these patches.

For this very reason, I'm not throwing the code away. :-)

*However*, if this happens, I don't think it will be soon, and
definitely not for Xen 4.13.

So, I'd say we should drop these items from this list.

Regards
-- 
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-08-02  9:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 16:00 [Xen-devel] [ANNOUNCE] Xen 4.13 Development Update Juergen Gross
2019-08-01 16:47 ` Andrew Cooper
2019-08-02  8:50   ` Wei Liu
2019-08-01 18:11 ` Roman Shaposhnik
2019-08-02  9:04   ` Roger Pau Monné
2019-08-02  9:57 ` Dario Faggioli [this message]
2019-08-02 15:52 ` Anthony PERARD
2019-08-02 17:07   ` Oleksandr
2019-08-12 10:02 ` Paul Durrant
  -- strict thread matches above, loose matches on Subject: below --
2019-09-28  5:09 Juergen Gross
2019-09-28 14:07 ` Steven Haigh
2019-09-06  7:40 Juergen Gross
2019-09-06 16:13 ` Andrew Cooper
2019-09-06 16:32 ` Konrad Rzeszutek Wilk
2019-09-09  7:52 ` Paul Durrant
2019-09-12  5:46 ` Chao Gao
2019-09-12  6:10 ` Roman Shaposhnik
2019-09-12  6:36   ` Juergen Gross
2019-09-13 16:19     ` Oleksandr
2019-07-01 11:35 Juergen Gross
2019-07-01 11:42 ` Jan Beulich
2019-07-01 12:09   ` Juergen Gross
2019-07-01 17:24 ` Volodymyr Babchuk
2019-05-28 10:54 Juergen Gross
2019-05-28 10:54 ` [Xen-devel] " Juergen Gross
2019-05-28 13:44 ` Tamas K Lengyel
2019-05-28 13:44   ` [Xen-devel] " Tamas K Lengyel
2019-05-28 23:07   ` Andrew Cooper
2019-05-28 23:07     ` [Xen-devel] " Andrew Cooper

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=8558ac91c3b555619a9866a339e4db20817ef626.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=jgross@suse.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).