Stephen,
thanks for summing it all up! I am guessing that a blueprint or updates
to an existing blueprint will be next. We currently have a patch that
introduces a second pin_set to nova.conf and solves problem1 and 2 in
ocata. But that might be overlooking a couple of cases we do not care
about/d
On 06/30/2017 07:06 AM, sfinu...@redhat.com wrote:
On Thu, 2017-06-29 at 12:20 -0600, Chris Friesen wrote:
On 06/29/2017 10:59 AM, sfinu...@redhat.com wrote:
From the above, there are 3-4 work items:
- Add a 'emulator_pin_set' or 'cpu_emulator_threads_mask' configuration
option
- If u
On Thu, 2017-06-29 at 12:20 -0600, Chris Friesen wrote:
> On 06/29/2017 10:59 AM, sfinu...@redhat.com wrote:
>
> > Thus far, we've no clear conclusions on directions to go, so I've took a
> > stab
> > below. Henning, Sahid, Chris: does the above/below make sense, and is there
> > anything we need
On 06/29/2017 10:59 AM, sfinu...@redhat.com wrote:
Thus far, we've no clear conclusions on directions to go, so I've took a stab
below. Henning, Sahid, Chris: does the above/below make sense, and is there
anything we need to further clarify?
The above is close enough. :)
# Problem 1
From t
On Tue, 2017-06-20 at 09:48 +0200, Henning Schild wrote:
> Hi,
>
> We are using OpenStack for managing realtime guests. We modified
> it and contributed to discussions on how to model the realtime
> feature. More recent versions of OpenStack have support for realtime,
> and there are a few proposa
Am Wed, 28 Jun 2017 11:34:42 +0200
schrieb Sahid Orentino Ferdjaoui :
> On Tue, Jun 27, 2017 at 04:00:35PM +0200, Henning Schild wrote:
> > Am Tue, 27 Jun 2017 09:44:22 +0200
> > schrieb Sahid Orentino Ferdjaoui :
> >
> > > On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote:
> > >
On 06/28/2017 03:34 AM, Sahid Orentino Ferdjaoui wrote:
On Tue, Jun 27, 2017 at 04:00:35PM +0200, Henning Schild wrote:
As far as i remember it was not straight forward to get two novas onto
one host in the older release, i am not surprised that causing trouble
with the update to mitaka. If we
On Tue, Jun 27, 2017 at 04:00:35PM +0200, Henning Schild wrote:
> Am Tue, 27 Jun 2017 09:44:22 +0200
> schrieb Sahid Orentino Ferdjaoui :
>
> > On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote:
> > > Am Sun, 25 Jun 2017 10:09:10 +0200
> > > schrieb Sahid Orentino Ferdjaoui :
> > >
On 06/27/2017 09:36 AM, Henning Schild wrote:
Am Tue, 27 Jun 2017 09:28:34 -0600
schrieb Chris Friesen :
Once you use "isolcpus" on the host, the host scheduler won't "float"
threads between the CPUs based on load. To get the float behaviour
you'd have to not isolate the pCPUs that will be us
Am Tue, 27 Jun 2017 09:25:14 -0600
schrieb Chris Friesen :
> On 06/27/2017 01:44 AM, Sahid Orentino Ferdjaoui wrote:
> > On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote:
> >> Am Sun, 25 Jun 2017 10:09:10 +0200
> >> schrieb Sahid Orentino Ferdjaoui :
> >>
> >>> On Fri, Jun 23, 20
Am Tue, 27 Jun 2017 09:28:34 -0600
schrieb Chris Friesen :
> On 06/27/2017 01:45 AM, Sahid Orentino Ferdjaoui wrote:
> > On Mon, Jun 26, 2017 at 12:12:49PM -0600, Chris Friesen wrote:
> >> On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote:
> >>> On Fri, Jun 23, 2017 at 10:34:26AM -0600, C
On 06/27/2017 01:45 AM, Sahid Orentino Ferdjaoui wrote:
On Mon, Jun 26, 2017 at 12:12:49PM -0600, Chris Friesen wrote:
On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote:
On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
On 06/23/2017 09:35 AM, Henning Schild wrote:
Am Fri, 2
On 06/27/2017 01:44 AM, Sahid Orentino Ferdjaoui wrote:
On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote:
Am Sun, 25 Jun 2017 10:09:10 +0200
schrieb Sahid Orentino Ferdjaoui :
On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
On 06/23/2017 09:35 AM, Henning Schild w
Am Tue, 27 Jun 2017 09:44:22 +0200
schrieb Sahid Orentino Ferdjaoui :
> On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote:
> > Am Sun, 25 Jun 2017 10:09:10 +0200
> > schrieb Sahid Orentino Ferdjaoui :
> >
> > > On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
> > >
On Mon, Jun 26, 2017 at 12:12:49PM -0600, Chris Friesen wrote:
> On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote:
> > On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
> > > On 06/23/2017 09:35 AM, Henning Schild wrote:
> > > > Am Fri, 23 Jun 2017 11:11:10 +0200
> > > > schrieb
On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote:
> Am Sun, 25 Jun 2017 10:09:10 +0200
> schrieb Sahid Orentino Ferdjaoui :
>
> > On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
> > > On 06/23/2017 09:35 AM, Henning Schild wrote:
> > > > Am Fri, 23 Jun 2017 11:11:10
On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote:
On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
On 06/23/2017 09:35 AM, Henning Schild wrote:
Am Fri, 23 Jun 2017 11:11:10 +0200
schrieb Sahid Orentino Ferdjaoui :
In Linux RT context, and as you mentioned, the non-RT vCP
Am Sun, 25 Jun 2017 10:09:10 +0200
schrieb Sahid Orentino Ferdjaoui :
> On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
> > On 06/23/2017 09:35 AM, Henning Schild wrote:
> > > Am Fri, 23 Jun 2017 11:11:10 +0200
> > > schrieb Sahid Orentino Ferdjaoui :
> >
> > > > In Linux RT
On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote:
> On 06/23/2017 09:35 AM, Henning Schild wrote:
> > Am Fri, 23 Jun 2017 11:11:10 +0200
> > schrieb Sahid Orentino Ferdjaoui :
>
> > > In Linux RT context, and as you mentioned, the non-RT vCPU can acquire
> > > some guest kernel lock,
On 06/23/2017 09:35 AM, Henning Schild wrote:
Am Fri, 23 Jun 2017 11:11:10 +0200
schrieb Sahid Orentino Ferdjaoui :
In Linux RT context, and as you mentioned, the non-RT vCPU can acquire
some guest kernel lock, then be pre-empted by emulator thread while
holding this lock. This situation block
Am Fri, 23 Jun 2017 11:11:10 +0200
schrieb Sahid Orentino Ferdjaoui :
> On Wed, Jun 21, 2017 at 12:47:27PM +0200, Henning Schild wrote:
> > Am Tue, 20 Jun 2017 10:04:30 -0400
> > schrieb Luiz Capitulino :
> >
> > > On Tue, 20 Jun 2017 09:48:23 +0200
> > > Henning Schild wrote:
> > >
> > > >
On Wed, Jun 21, 2017 at 12:47:27PM +0200, Henning Schild wrote:
> Am Tue, 20 Jun 2017 10:04:30 -0400
> schrieb Luiz Capitulino :
>
> > On Tue, 20 Jun 2017 09:48:23 +0200
> > Henning Schild wrote:
> >
> > > Hi,
> > >
> > > We are using OpenStack for managing realtime guests. We modified
> > > it
On 06/22/2017 01:47 AM, Henning Schild wrote:
Am Wed, 21 Jun 2017 11:40:14 -0600
schrieb Chris Friesen :
On 06/21/2017 10:46 AM, Henning Schild wrote:
As we know from our setup, and as Luiz confirmed - it is _not_
"critical to separate emulator threads for different KVM instances".
They have
Am Wed, 21 Jun 2017 11:40:14 -0600
schrieb Chris Friesen :
> On 06/21/2017 10:46 AM, Henning Schild wrote:
> > Am Wed, 21 Jun 2017 10:04:52 -0600
> > schrieb Chris Friesen :
>
> > i guess you are talking about that section from [1]:
> >
> We could use a host level tunable to just reserve
On 06/21/2017 10:46 AM, Henning Schild wrote:
Am Wed, 21 Jun 2017 10:04:52 -0600
schrieb Chris Friesen :
i guess you are talking about that section from [1]:
We could use a host level tunable to just reserve a set of host
pCPUs for running emulator threads globally, instead of trying to
acco
Am Wed, 21 Jun 2017 10:04:52 -0600
schrieb Chris Friesen :
> On 06/21/2017 09:45 AM, Chris Friesen wrote:
> > On 06/21/2017 02:42 AM, Henning Schild wrote:
> >> Am Tue, 20 Jun 2017 10:41:44 -0600
> >> schrieb Chris Friesen :
> >
> Our goal is to reach a high packing density of realtime
On 06/21/2017 02:42 AM, Henning Schild wrote:
Am Tue, 20 Jun 2017 10:41:44 -0600
schrieb Chris Friesen :
Our goal is to reach a high packing density of realtime VMs. Our
pragmatic first choice was to run all non-vcpu-threads on a shared
set of pcpus where we also run best-effort VMs and host l
Am Wed, 21 Jun 2017 09:32:42 -0400
schrieb Luiz Capitulino :
> On Wed, 21 Jun 2017 12:47:27 +0200
> Henning Schild wrote:
>
> > > What is your solution?
> >
> > We have a kilo-based prototype that introduced emulator_pin_set in
> > nova.conf. All vcpu threads will be scheduled on vcpu_pin_s
Am Tue, 20 Jun 2017 10:04:30 -0400
schrieb Luiz Capitulino :
> On Tue, 20 Jun 2017 09:48:23 +0200
> Henning Schild wrote:
>
> > Hi,
> >
> > We are using OpenStack for managing realtime guests. We modified
> > it and contributed to discussions on how to model the realtime
> > feature. More recen
Am Tue, 20 Jun 2017 10:41:44 -0600
schrieb Chris Friesen :
> On 06/20/2017 01:48 AM, Henning Schild wrote:
> > Hi,
> >
> > We are using OpenStack for managing realtime guests. We modified
> > it and contributed to discussions on how to model the realtime
> > feature. More recent versions of OpenSt
On 06/20/2017 01:48 AM, Henning Schild wrote:
Hi,
We are using OpenStack for managing realtime guests. We modified
it and contributed to discussions on how to model the realtime
feature. More recent versions of OpenStack have support for realtime,
and there are a few proposals on how to improve
Hi,
We are using OpenStack for managing realtime guests. We modified
it and contributed to discussions on how to model the realtime
feature. More recent versions of OpenStack have support for realtime,
and there are a few proposals on how to improve that further.
But there is still no full answer
32 matches
Mail list logo
