All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kinzler <ml-ak@posteo.de>
To: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: state of xenified SUSE kernel
Date: Wed, 18 May 2016 16:39:44 +0200	[thread overview]
Message-ID: <573C7EB0.9070202@posteo.de> (raw)
In-Reply-To: <573B560E02000078000EC442@prv-mh.provo.novell.com>

On 17.05.2016 17:34, Jan Beulich wrote:
>> We use xenified kernels based on kernel 3.4 for years and benchmarks
>> showed that they are faster than the pvops (vanilla) kernels.
>> But what is the current state in terms of performance and features?
> I'm not sure what you expect here. Up to openSUSE 42.1 and
> SLE 12 SP1 they are fully maintained, i.e. you can get quite a
> bit newer than 3.4 based kernels. There's not a lot of
> performance analysis that I would be aware of, so I can't
> answer that part anyway. And them being release branches
> rather than development ones, there's not going to be any
> new feature work.

As far as I know the patches are based on the original work for kernel 
2.6.18 and have not been adjusted to major changes in Xen architecture. 
So what I am thinking about is performance improvements that result from 
using newer Xen features. So the question was: from an architectural 
point of view should pvops in recent vanilla kernels be "better" then 
xenified kernels?

Regards Andreas

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

  reply	other threads:[~2016-05-18 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 15:10 state of xenified SUSE kernel Andreas Kinzler
2016-05-17 15:34 ` Jan Beulich
2016-05-18 14:39   ` Andreas Kinzler [this message]
2016-05-18 15:15     ` Jan Beulich

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=573C7EB0.9070202@posteo.de \
    --to=ml-ak@posteo.de \
    --cc=JBeulich@suse.com \
    --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.