qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/2] aio: Introduce aio-epoll.c
Date: Fri, 16 Oct 2015 18:10:47 +0800	[thread overview]
Message-ID: <20151016101047.GA16813@ad.usersys.redhat.com> (raw)
In-Reply-To: <20151016093231.GH7432@stefanha-thinkpad.redhat.com>

On Fri, 10/16 11:32, Stefan Hajnoczi wrote:
> On Tue, Oct 13, 2015 at 07:10:55PM +0800, Fam Zheng wrote:
> > +static bool aio_epoll_try_enable(AioContext *ctx)
> > +{
> > +    AioHandler *node;
> > +    struct epoll_event event;
> > +    if (!ctx->epoll_available) {
> > +        return false;
> > +    }
> 
> Why check this here since aio_epoll_check_poll() already checks it?

You're right, it's redundant. I will remove it.

> 
> > +static int aio_epoll(AioContext *ctx, GPollFD *pfds,
> > +                     unsigned npfd, int64_t timeout)
> > +{
> > +    AioHandler *node;
> > +    int i, ret = 0;
> > +    struct epoll_event events[128];
> 
> The strategy is to support up to 128 events per epoll_wait(2) call and
> then wait for the next event loop iteration to harvest any remaining
> events?

Yes.

      reply	other threads:[~2015-10-16 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 11:10 [Qemu-devel] [PATCH v2 0/2] aio: Use epoll in aio_poll() Fam Zheng
2015-10-13 11:10 ` [Qemu-devel] [PATCH v2 1/2] aio: Introduce aio_context_setup Fam Zheng
2015-10-13 11:10 ` [Qemu-devel] [PATCH v2 2/2] aio: Introduce aio-epoll.c Fam Zheng
2015-10-16  9:32   ` Stefan Hajnoczi
2015-10-16 10:10     ` Fam Zheng [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=20151016101047.GA16813@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).