All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org, ldoktor@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.13] pc-bios/s390-ccw: Increase virtio timeout to 30 seconds
Date: Thu, 29 Mar 2018 13:02:06 +0200	[thread overview]
Message-ID: <20180329130206.0b33b040.cohuck@redhat.com> (raw)
In-Reply-To: <2103b547-66aa-d1f7-a504-cb6ef3672039@de.ibm.com>

On Thu, 29 Mar 2018 12:03:42 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> On 03/29/2018 11:37 AM, Thomas Huth wrote:
> > The current timeout is set to only three seconds - and considering that
> > vring_wait_reply() or rather get_second() is not doing any rounding,
> > the real timeout is likely rather 2 seconds in most cases. When the
> > host is really badly loaded and we run the guest in TCG mode instead
> > of KVM, it's possible that we hit this timeout by mistake. So let's
> > increase the timeout to 30 seconds instead to ease this situation (30
> > seconds is also the timeout that is used by the Linux SCSI subsystem
> > for example, so this seems to be a sane value for block IO timeout).  
> 
> I have never seen this, but cant this also with KVM (e.g. host paging
> and the swap disk is busy for some seconds).

It's probably less likely, but I don't see why not. 30s sounds like a
more forgiving value.

> 
> Wouldnt it also qualify for 2.12?

I can queue it (and a bios rebuild) to s390-fixes, it's certainly
reasonable.

Else,

Reviewed-by: Cornelia Huck <cohuck@redhat.com>

> 
> > 
> > Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1549079
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> >  pc-bios/s390-ccw/virtio.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/pc-bios/s390-ccw/virtio.c b/pc-bios/s390-ccw/virtio.c
> > index 817e7f5..cdb66f4 100644
> > --- a/pc-bios/s390-ccw/virtio.c
> > +++ b/pc-bios/s390-ccw/virtio.c
> > @@ -14,7 +14,7 @@
> >  #include "virtio-scsi.h"
> >  #include "bswap.h"
> > 
> > -#define VRING_WAIT_REPLY_TIMEOUT 3
> > +#define VRING_WAIT_REPLY_TIMEOUT 30
> > 
> >  static VRing block[VIRTIO_MAX_VQS];
> >  static char ring_area[VIRTIO_RING_SIZE * VIRTIO_MAX_VQS]
> >   
> 

  reply	other threads:[~2018-03-29 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  9:37 [Qemu-devel] [PATCH for-2.13] pc-bios/s390-ccw: Increase virtio timeout to 30 seconds Thomas Huth
2018-03-29 10:03 ` Christian Borntraeger
2018-03-29 11:02   ` Cornelia Huck [this message]
2018-03-29 11:32   ` Thomas Huth
2018-03-29 11:46 ` Christian Borntraeger
2018-03-29 13:15 ` Cornelia Huck
2018-03-29 13:23   ` Thomas Huth
2018-03-29 14:34 ` Cornelia Huck
2018-03-31  6:28 ` no-reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180329130206.0b33b040.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=ldoktor@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.