On Apr 21, 2015, at 09:21 , Eyal Edri ee...@redhat.com wrote:
- Original Message -
From: Michal Skrivanek michal.skriva...@redhat.com
To: Nir Soffer nsof...@redhat.com, Max Kovgan mkov...@redhat.com
Cc: Dan Kenigsberg dan...@redhat.com, Eyal Edri ee...@redhat.com,
On Apr 21, 2015, at 06:14 , Eyal Edri ee...@redhat.com wrote:
Adding max
Sent from Nine
From: Nir Soffer
Sent: Apr 21, 2015 2:59 AM
To: Dan Kenigsberg
Cc:
msi...@redhat.com;mpoled...@redhat.com;ee...@redhat.com;devel@ovirt.org;dc...@redhat.com;do...@redhat.com
Subject: Re: [oVirt
- Original Message -
From: Michal Skrivanek michal.skriva...@redhat.com
To: Eyal Edri ee...@redhat.com
Cc: Dan Kenigsberg dan...@redhat.com, Nir Soffer nsof...@redhat.com,
Max Kovgan mkov...@redhat.com,
dc...@redhat.com, do...@redhat.com, mpoled...@redhat.com, devel@ovirt.org
- Original Message -
From: Michal Skrivanek michal.skriva...@redhat.com
To: Nir Soffer nsof...@redhat.com, Max Kovgan mkov...@redhat.com
Cc: Dan Kenigsberg dan...@redhat.com, Eyal Edri ee...@redhat.com,
dc...@redhat.com, do...@redhat.com,
mpoled...@redhat.com, devel@ovirt.org
On the current old job yes, that's ignored, but on the new one that has been
waiting for any vdsm devel to fix for quite some time, that's not an issue:
http://jenkins.ovirt.org/job/vdsm_master_unit-tests_created_staging/
On 04/21, Michal Skrivanek wrote:
On Apr 21, 2015, at 06:14 , Eyal
Greetings users and developers,
Just put up a feature page for the NUMA aware KSM support;
In summary,
===
The KSM service is optimizing shared memory pages across all NUMA nodes. The
consequences is: a shared memory pages (controlled by KSM) to be read from many
CPUs across NUMA
On 04/21/2015 01:43 PM, Liran Zelkha wrote:
Hi
After a very long development cycle, we have finally introduced CDI
and JPA technologies into oVirt.
This means that in the next few month you'll see more and more of our
stored procedures replaced with JPA code, which will allow us to have
Hi
After a very long development cycle, we have finally introduced CDI and JPA
technologies into oVirt.
This means that in the next few month you'll see more and more of our
stored procedures replaced with JPA code, which will allow us to have
easier entity mapping and enjoy performance boost