All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ISCSI: We need to call qemu_notify_event() everytime we update which events we need to be notified for.
Date: Tue, 22 May 2012 14:13:40 +0200	[thread overview]
Message-ID: <jpfvtk$64i$1@dough.gmane.org> (raw)
In-Reply-To: <1337680596-8485-1-git-send-email-ronniesahlberg@gmail.com>

Il 22/05/2012 11:56, Ronnie Sahlberg ha scritto:
> Otherwise, If we add an event for -is-writeable but the socket is already writeable there may be a short delay before the event callback is actually triggered.
> 
> Those delays would in particular hurt performance during BIOS boot and when the GRUB bootloader reads the kernel and initrd.
> 
> Signed-off-by: Ronnie Sahlberg <ronniesahlberg@gmail.com>
> ---
>  block/iscsi.c |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
> 
> diff --git a/block/iscsi.c b/block/iscsi.c
> index d37c4ee..f956824 100644
> --- a/block/iscsi.c
> +++ b/block/iscsi.c
> @@ -109,6 +109,13 @@ iscsi_set_events(IscsiLun *iscsilun)
>                             (iscsi_which_events(iscsi) & POLLOUT)
>                             ? iscsi_process_write : NULL,
>                             iscsi_process_flush, iscsilun);
> +
> +    /* If we just added the event for writeable we must call
> +       and the socket is already writeable the callback might
> +       not be invoked until after a short delay unless we call
> +       qemu_notify_event().
> +     */
> +    qemu_notify_event();
>  }
>  
>  static void

Thanks, applied to SCSI branch for 1.1.

Paolo

      reply	other threads:[~2012-05-22 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  9:56 [Qemu-devel] [PATCH] ISCSI: We need to call qemu_notify_event() everytime we update which events we need to be notified for Ronnie Sahlberg
2012-05-22 12:13 ` Paolo Bonzini [this message]

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='jpfvtk$64i$1@dough.gmane.org' \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.