similar to: glm predict issue

Hello, I have one replication (r=1 of the 2^k*r) of a 2^k experimental design in the context of performance analysis i.e. my response variables are Throughput and Response Time. I use the "aov" function and the results look ok: > str(throughput) 'data.frame': 286 obs. of 7 variables: $ Time : int 6 7 8 9 10 11 12 13 14 15 ... $ Throughput : int 42 44 33 41

Hello, When I try to use TukeyHSD in the following way it shows the confidence interval corresponding to the last factor only. > throughput.aov <- aov(Throughput~No_databases+Partitioning+No_middlewares+Queue_size,data=throughput) plot(TukeyHSD(throughput.aov)) # I expected here to see the confidence intervals for all factors but see only the last. OTOH this one works but then it is

Hello, I currently get anova results out of the aov function (see below) I use the model.tables and I believe it gives me back the model parameters of the fit (betas), however I don't see the intercept (beta_0) and don't understand what the "rep" output means and there is no description in the documentation. Another question: is there a function that outputs the results in a

Hello, I currently run aov in the following way: > throughput.aov <- aov(log(Throughput)~No_databases+Partitioning+No_middlewares+Queue_size,data=throughput) > summary(throughput.aov) Df Sum Sq Mean Sq F value Pr(>F) No_databases 1 184.68 184.675 136.6945 < 2.2e-16 *** Partitioning 1 70.16 70.161 51.9321 2.516e-12 *** No_middlewares 2 44.22

From: Jorgen Hansen <jhansen at vmware.com> The current maximum size of a queue in a queue pair is 128 MB. If we increase that in the future, the queue pair allocation routines may run into overflow issues. This change adds additional checks to guard against this. Acked-by: Andy King <acking at vmware.com> Reported-by: Dan Carpenter <dan.carpenter at oracle.com> Signed-off-by:

From: Jorgen Hansen <jhansen at vmware.com> The current maximum size of a queue in a queue pair is 128 MB. If we increase that in the future, the queue pair allocation routines may run into overflow issues. This change adds additional checks to guard against this. Acked-by: Andy King <acking at vmware.com> Reported-by: Dan Carpenter <dan.carpenter at oracle.com> Signed-off-by:

This patch adds support for virtual IOMMU to the vmci module. We switch to DMA consistent mappings for guest queuepair and doorbell pages that are passed to the device. We still allocate each page individually, since there's no guarantee that we'll get a contiguous block of physical for an entire queuepair (especially since we allow up to 128 MiB!). Also made the split between guest and

On Wed, May 29, 2013 at 02:01:18PM +0930, Rusty Russell wrote: > Anthony Liguori <aliguori at us.ibm.com> writes: > > "Michael S. Tsirkin" <mst at redhat.com> writes: > >> + case offsetof(struct virtio_pci_common_cfg, device_feature_select): > >> + return proxy->device_feature_select; > > > > Oh dear no... Please use

dovecot-auth hangs when many (>128) LDAP queries are submited simultaneously. (for example via pop3 benchmarking tool). Bug is in src/auth/db-ldap.c:db_ldap_request_queue_next if (queue_size > DB_LDAP_MAX_PENDING_REQUESTS) { /* wait until server has replied to some requests */ return FALSE; } (queue_size is total queue size, not only

- queue size can actually be 0 which is not a power of 2 - fix capability format. PCI spec says: The layout of the information is vendor specific, except that the byte immediately following the ?Next? pointer in the capability structure is defined to be a length field. This length field provides the number of bytes in the capability structure (including the ID and Next pointer bytes).

From 80b234220ea85d6fb291b0509ce2b3322e5ecc1f Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:07:16 +0200 Subject: [PATCH] [PATCH 1/3] virtio infrastructure This patch implements the basic infrastructure for virtio devices. These devices are exposed to the guest as real PCI devices. The PCI vendor/device IDs have been donated by Qumranet and the

From 80b234220ea85d6fb291b0509ce2b3322e5ecc1f Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:07:16 +0200 Subject: [PATCH] [PATCH 1/3] virtio infrastructure This patch implements the basic infrastructure for virtio devices. These devices are exposed to the guest as real PCI devices. The PCI vendor/device IDs have been donated by Qumranet and the

In this commit, virtqueue operations including: set_vq_num(), set_vq_address(), set_vq_ready() and get_vq_ready() access PCI registers directly to take immediate actions. Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> --- drivers/vdpa/ifcvf/ifcvf_base.c | 58 ++++++++++++++++++++------------- drivers/vdpa/ifcvf/ifcvf_base.h | 10 +++--- drivers/vdpa/ifcvf/ifcvf_main.c | 16

In this commit, virtqueue operations including: set_vq_num(), set_vq_address(), set_vq_ready() and get_vq_ready() access PCI registers directly to take immediate actions. Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> --- drivers/vdpa/ifcvf/ifcvf_base.c | 58 ++++++++++++++++++++------------- drivers/vdpa/ifcvf/ifcvf_base.h | 10 +++--- drivers/vdpa/ifcvf/ifcvf_main.c | 16

Since PCI is little endian, 8-bit access might work, but the spec section is very clear on this: 4.1.3.1 Driver Requirements: PCI Device Layout The driver MUST access each field using the ?natural? access method, i.e. 32-bit accesses for 32-bit fields, 16-bit accesses for 16-bit fields and 8-bit accesses for 8-bit fields. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au>

Since PCI is little endian, 8-bit access might work, but the spec section is very clear on this: 4.1.3.1 Driver Requirements: PCI Device Layout The driver MUST access each field using the ?natural? access method, i.e. 32-bit accesses for 32-bit fields, 16-bit accesses for 16-bit fields and 8-bit accesses for 8-bit fields. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au>

"Michael S. Tsirkin" <mst at redhat.com> writes: > This adds support for new config, and is designed to work with > the new layout code in Rusty's new layout branch. > > At the moment all fields are in the same memory BAR (bar 2). > This will be used to test performance and compare > memory, io and hypercall latency. > > Compiles but does not work yet.

This adds (incomplete) MSI-X support to virtio net device. Missing is save/load support, and command-line flag to control the feature. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 362 +++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 33 +++++ hw/pci.c | 35 ++++-- hw/pci.h

This adds (incomplete) MSI-X support to virtio net device. Missing is save/load support, and command-line flag to control the feature. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 362 +++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 33 +++++ hw/pci.c | 35 ++++-- hw/pci.h

From: Rusty Russell <rusty at rustcorp.com.au> Based on patches by Michael S. Tsirkin <mst at redhat.com>, but I found it hard to follow so changed to use structures which are more self-documenting. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- include/uapi/linux/virtio_pci.h | 62