similar to: virtio ring layout changes for optimal single-stream performance

On Thu, 21 Jan 2016 15:39:26 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Hi all! > I have been experimenting with alternative virtio ring layouts, > in order to speed up single stream performance. > > I have just posted a benchmark I wrote for the purpose, and a (partial) > alternative layout implementation. This achieves 20-40% reduction in >

This adds micro-benchmarks useful for tuning virtio ring layouts. Three layouts are currently implemented: - virtio 0.9 compatible one - an experimental extension bypassing the ring index, polling ring itself instead - an experimental extension bypassing avail and used ring completely Typical use: sh run-on-all.sh perf stat -r 10 --log-fd 1 -- ./ring It doesn't depend on the kernel

This adds micro-benchmarks useful for tuning virtio ring layouts. Three layouts are currently implemented: - virtio 0.9 compatible one - an experimental extension bypassing the ring index, polling ring itself instead - an experimental extension bypassing avail and used ring completely Typical use: sh run-on-all.sh perf stat -r 10 --log-fd 1 -- ./ring It doesn't depend on the kernel

Michael, the following patches have all been posted in the past. I've collected them on top of your vhost branch -- please let me know whether this works for you. The following changes since commit 6bdf1e0efb04a1716373646cb6f35b73addca492: Makefile: drop -D__CHECK_ENDIAN__ from cflags (2016-12-16 00:13:43 +0200) are available in the git repository at:

Michael, the following patches have all been posted in the past. I've collected them on top of your vhost branch -- please let me know whether this works for you. The following changes since commit 6bdf1e0efb04a1716373646cb6f35b73addca492: Makefile: drop -D__CHECK_ENDIAN__ from cflags (2016-12-16 00:13:43 +0200) are available in the git repository at:

Hi In asterisk 1.8.7.0, an inbound call that was transferred to another peer would have 2 cdr entries. In asterisk 1.8.18.0 this same activity has a single cdr entry. This is a rather large and fundamental change to be enacting halfway through a single family branch, was there any reason why this happened? It means we can't upgrade without doing significant extra development and testing.

After some months of "Make updates", I have just deleted my Zaptel and Asterisk source directories and done "cvs checkout" 's of asterisk and zaptel, in order to clean up the trees. After re-installing, I am finding that when dialling into an X100P, that Answer is now answering on the second ring, where it always used to answer on the first before. In the console,

From: Halil Pasic <pasic at linux.vnet.ibm.com> Make ringtest work on s390 too. Signed-off-by: Halil Pasic <pasic at linux.vnet.ibm.com> Acked-by: Sascha Silbe <silbe at linux.vnet.ibm.com> Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- tools/virtio/ringtest/main.h | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git

Hi, I am referring to https://wiki.centos.org/Manuals/ReleaseNotes/CentOSStream and i am not sure if i understand it correctly, Is it a separate CentOS distribution which is similar to CentOS-8 (1905)? Thanks in advance and i look forward to hearing from you. Best Regards, Kaushal

On Sat, Oct 05, 2019 at 03:01:43PM +0100, Pete Biggs wrote: > In the future new features and upgrades will appear in Stream as a sort > of rolling release and it will form the basis of future RHEL releases > (and subsequently CentOS releases). It will also be the place for > community input into RHEL/CentOS. Think of it as halfway between the > cutting edge Fedora and the stable

On Wed, Mar 08, 2017 at 03:09:48PM +0800, Yuanhan Liu wrote: > On Wed, Mar 01, 2017 at 03:07:29AM +0200, Michael S. Tsirkin wrote: > > On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > > > Hi Michael, > > > > > > Again, as usual, sorry for being late :/ > > > > > > On Wed, Feb 22, 2017 at 06:27:11AM +0200, Michael S. Tsirkin

On Wed, Mar 08, 2017 at 03:09:48PM +0800, Yuanhan Liu wrote: > On Wed, Mar 01, 2017 at 03:07:29AM +0200, Michael S. Tsirkin wrote: > > On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > > > Hi Michael, > > > > > > Again, as usual, sorry for being late :/ > > > > > > On Wed, Feb 22, 2017 at 06:27:11AM +0200, Michael S. Tsirkin

On 08/02/2017 20:59, Michael S. Tsirkin wrote: > We couldn't decide what's better for everyone in 1.0 days and I doubt > we'll be able to now, but yes, benchmarking is needed to make > sire it's required. Very easy to remove or not to use/support in > drivers/devices though. Fair enough, but of course then we must specify that devices MUST support either

On Wed, Mar 01, 2017 at 03:07:29AM +0200, Michael S. Tsirkin wrote: > On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > > Hi Michael, > > > > Again, as usual, sorry for being late :/ > > > > On Wed, Feb 22, 2017 at 06:27:11AM +0200, Michael S. Tsirkin wrote: > > > Stage 2: prototype guest/host drivers > > > > > > At this

On Wed, Mar 08, 2017 at 03:56:24PM +0800, Yuanhan Liu wrote: > On Wed, Mar 08, 2017 at 03:09:48PM +0800, Yuanhan Liu wrote: > > On Wed, Mar 01, 2017 at 03:07:29AM +0200, Michael S. Tsirkin wrote: > > > On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > > > > Hi Michael, > > > > > > > > Again, as usual, sorry for being late :/ >

On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > Hi Michael, > > Again, as usual, sorry for being late :/ > > On Wed, Feb 22, 2017 at 06:27:11AM +0200, Michael S. Tsirkin wrote: > > Stage 2: prototype guest/host drivers > > > > At this stage we need real guest and host drivers > > to be able to test real life performance. > > I suggest

On Tue, Feb 28, 2017 at 12:29:43PM +0800, Yuanhan Liu wrote: > Hi Michael, > > Again, as usual, sorry for being late :/ > > On Wed, Feb 22, 2017 at 06:27:11AM +0200, Michael S. Tsirkin wrote: > > Stage 2: prototype guest/host drivers > > > > At this stage we need real guest and host drivers > > to be able to test real life performance. > > I suggest

> On Sep 4, 2020, at 2:40 PM, Neil Nelson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> If fptosi takes 0.9 -> 0, then that is not 'rounding' in any sense I'm aware of (IEEE754 or otherwise). >> Rounding (in the IEE754 sense) determines how a number is converted when it is halfway between two >> candidate results. (see round(), ceil(),

On Thu, Feb 09, 2017 at 04:48:53PM +0100, Paolo Bonzini wrote: > > > On 08/02/2017 20:59, Michael S. Tsirkin wrote: > > We couldn't decide what's better for everyone in 1.0 days and I doubt > > we'll be able to now, but yes, benchmarking is needed to make > > sire it's required. Very easy to remove or not to use/support in > > drivers/devices

On Thu, Feb 09, 2017 at 04:48:53PM +0100, Paolo Bonzini wrote: > > > On 08/02/2017 20:59, Michael S. Tsirkin wrote: > > We couldn't decide what's better for everyone in 1.0 days and I doubt > > we'll be able to now, but yes, benchmarking is needed to make > > sire it's required. Very easy to remove or not to use/support in > > drivers/devices