similar to: [PATCH 2/3] virtio: indirect ring entries (VIRTIO_RING_F_INDIRECT_DESC)

Hi Rusty, On Thu, 2008-12-18 at 17:10 +0000, Mark McLoughlin wrote: > Add a new feature flag for indirect ring entries. These are ring > entries which point to a table of buffer descriptors. > > The idea here is to increase the ring capacity by allowing a larger > effective ring size whereby the ring size dictates the number of > requests that may be outstanding, rather than

Hi Rusty, On Thu, 2008-12-18 at 17:10 +0000, Mark McLoughlin wrote: > Add a new feature flag for indirect ring entries. These are ring > entries which point to a table of buffer descriptors. > > The idea here is to increase the ring capacity by allowing a larger > effective ring size whereby the ring size dictates the number of > requests that may be outstanding, rather than

Dear ext3-users, we hit this condition in fs/ext3/inode.c:ext3_block_to_path() if (i_block < 0) { ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0"); occasionally on two identical PATA-IDE disks copied over per filesystem-rsync. What is the impact of this condition? - Kernel was 2.6.13.4, CONFIG_LBD is not set but CONFIG_HIGHMEM4G=y

On 2020/6/11 ??7:34, Michael S. Tsirkin wrote: > static void vhost_vq_free_iovecs(struct vhost_virtqueue *vq) > { > kfree(vq->descs); > @@ -394,6 +400,9 @@ static long vhost_dev_alloc_iovecs(struct vhost_dev *dev) > for (i = 0; i < dev->nvqs; ++i) { > vq = dev->vqs[i]; > vq->max_descs = dev->iov_limit; > + if

On 2020/6/11 ??7:34, Michael S. Tsirkin wrote: > static void vhost_vq_free_iovecs(struct vhost_virtqueue *vq) > { > kfree(vq->descs); > @@ -394,6 +400,9 @@ static long vhost_dev_alloc_iovecs(struct vhost_dev *dev) > for (i = 0; i < dev->nvqs; ++i) { > vq = dev->vqs[i]; > vq->max_descs = dev->iov_limit; > + if

Rather than handing a scatterlist[] and out and in numbers to virtqueue_add_buf(), hand two separate ones which can be chained. I shall refrain from ranting about what a disgusting hack chained scatterlists are. I'll just note that this doesn't make things simpler (see diff). The scatterlists we use can be too large for the stack, so we put them in our device struct and reuse them. But

Rather than handing a scatterlist[] and out and in numbers to virtqueue_add_buf(), hand two separate ones which can be chained. I shall refrain from ranting about what a disgusting hack chained scatterlists are. I'll just note that this doesn't make things simpler (see diff). The scatterlists we use can be too large for the stack, so we put them in our device struct and reuse them. But

On 2020/6/23 ??3:00, Eugenio Perez Martin wrote: > On Tue, Jun 23, 2020 at 4:51 AM Jason Wang <jasowang at redhat.com> wrote: >> >> On 2020/6/23 ??12:00, Michael S. Tsirkin wrote: >>> On Wed, Jun 17, 2020 at 11:19:26AM +0800, Jason Wang wrote: >>>> On 2020/6/11 ??7:34, Michael S. Tsirkin wrote: >>>>> static void

On Tue, Jun 23, 2020 at 09:00:57AM +0200, Eugenio Perez Martin wrote: > On Tue, Jun 23, 2020 at 4:51 AM Jason Wang <jasowang at redhat.com> wrote: > > > > > > On 2020/6/23 ??12:00, Michael S. Tsirkin wrote: > > > On Wed, Jun 17, 2020 at 11:19:26AM +0800, Jason Wang wrote: > > >> On 2020/6/11 ??7:34, Michael S. Tsirkin wrote: > > >>>

Okay, as of this point, I think klibc is in quite good shape; my testing so far is showing that it can be used as a drop-in replacement for the kernel root-mounting code. That being said, there is guaranteed to be breakage, for two reasons: a. There are several architectures which don't have klibc ports yet. Since I don't have access to them, I can't really do them, either.

virtqueue_add() populates the virtqueue descriptor table from the sgs given. If it uses an indirect descriptor table, then it puts a single descriptor in the descriptor table pointing to the kmalloc'ed indirect table where the sg is populated. Previously vring_add_indirect() did the allocation and the simple linear layout. We replace that with alloc_indirect() which allocates the indirect

On 5/6/2015 1:18 PM, Leon Fauster wrote: > Am 06.05.2015 um 09:33 schrieb Jatin Davey <jashokda at cisco.com>: >> My guest is a CentOS 5.4 VM: > > Best practice: update to the latest OS version: > > # cat /etc/redhat-release > CentOS release 5.11 (Final) > > > >> [root at localhost ~]# uname -a >> Linux localhost 2.6.18-164.el5 #1 SMP Thu Sep 3

On 05/06/2015 03:04 AM, Jatin Davey wrote: > On 5/6/2015 1:18 PM, Leon Fauster wrote: >> Am 06.05.2015 um 09:33 schrieb Jatin Davey <jashokda at cisco.com>: >>> My guest is a CentOS 5.4 VM: >> >> Best practice: update to the latest OS version: >> >> # cat /etc/redhat-release >> CentOS release 5.11 (Final) >> >> >> >>>

With 2.6.31-rc5 in a KVM guest using dm and virtio_blk, we see the following errors: end_request: I/O error, dev vda, sector 0 end_request: I/O error, dev vda, sector 0 The errors go away if dm stops submitting empty barriers, by reverting: commit 52b1fd5a27c625c78373e024bf570af3c9d44a79 Author: Mikulas Patocka <mpatocka at redhat.com> dm: send empty barriers to targets in

With 2.6.31-rc5 in a KVM guest using dm and virtio_blk, we see the following errors: end_request: I/O error, dev vda, sector 0 end_request: I/O error, dev vda, sector 0 The errors go away if dm stops submitting empty barriers, by reverting: commit 52b1fd5a27c625c78373e024bf570af3c9d44a79 Author: Mikulas Patocka <mpatocka at redhat.com> dm: send empty barriers to targets in

Hi All My guest is a CentOS 5.4 VM: [root at localhost ~]# uname -a Linux localhost 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [root at localhost ~]# cat /etc/*release CentOS release 5.4 (Final) I wanted to know if the virtio drivers on this guest are stable. The reason for asking this question is that i found this link:

From: Mark McLoughlin <markmc at redhat.com> hdr->csum_start is the offset from the start of the ethernet header to the transport layer checksum field. skb->csum_start is the offset from skb->head. skb_partial_csum_set() assumes that skb->data points to the ethernet header - i.e. it computes skb->csum_start by adding the headroom to hdr->csum_start. Since

(Moved from kvm at vger to virtualization at linux-foundation, changed subject, cleaned up cc list) On Wed, 2008-12-10 at 13:02 +0100, Kay Sievers wrote: > On Wed, Dec 10, 2008 at 10:49, Mark McLoughlin <markmc at redhat.com> wrote: > > On Tue, 2008-12-09 at 19:16 +0100, Kay Sievers wrote: > >> On Tue, Dec 9, 2008 at 17:41, Mark McLoughlin <markmc at redhat.com>

(Moved from kvm at vger to virtualization at linux-foundation, changed subject, cleaned up cc list) On Wed, 2008-12-10 at 13:02 +0100, Kay Sievers wrote: > On Wed, Dec 10, 2008 at 10:49, Mark McLoughlin <markmc at redhat.com> wrote: > > On Tue, 2008-12-09 at 19:16 +0100, Kay Sievers wrote: > >> On Tue, Dec 9, 2008 at 17:41, Mark McLoughlin <markmc at redhat.com>

Hello > I am wondering if the modification made to the DAG is causing a problem, and > can it be done at all? If I cannot do this, is there any other place I can > look at, to make this work. It's hard to tell w/o seeing the exact code / DAG. Note, however, that this assertion is seen on simple LLVM IR: http://llvm.org/bugs/show_bug.cgi?id=15053 So, it might be not your bug after