All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Mao Zhongyi <maozy.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
	mitake.hitoshi@lab.ntt.co.jp, jcody@redhat.com,
	mreitz@redhat.com, sheepdog@lists.wpkg.org,
	Cao jin <caoj.fnst@cn.fujitsu.com>,
	kraxel@redhat.com, pbonzini@redhat.com, namei.unix@gmail.com
Subject: Re: [Qemu-devel] [PATCH] util: remove the obsolete non-blocking connect
Date: Thu, 15 Jun 2017 09:34:40 +0200	[thread overview]
Message-ID: <87mv99aelr.fsf@secure.mitica> (raw)
In-Reply-To: <20170615030801.6260-1-maozy.fnst@cn.fujitsu.com> (Mao Zhongyi's message of "Thu, 15 Jun 2017 11:08:01 +0800")

Mao Zhongyi <maozy.fnst@cn.fujitsu.com> wrote:
> From: Cao jin <caoj.fnst@cn.fujitsu.com>
>
> The non-blocking connect mechanism is obsolete, and it doesn't
> work well in inet connection, because it will call getaddrinfo
> first and getaddrinfo will blocks on DNS lookups. Since commit
> e65c67e4 & d984464e, the non-blocking connect of migration goes
> through QIOChannel in a different manner(using a thread), and
> nobody use this old non-blocking connect anymore.
>
> Any newly written code which needs a non-blocking connect should
> use the QIOChannel code, so we can drop NonBlockingConnectHandler


Reviewed-by: Juan Quintela <quintela@redhat.com>


...

>  int inet_connect_saddr(InetSocketAddress *saddr,
> -                       NonBlockingConnectHandler *callback, void *opaque,
>                         Error **errp);

In case you have to respin it.

Now you can write the prototype in a single line, no?
Same for the rest of appearances.

  parent reply	other threads:[~2017-06-15  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15  3:08 [Qemu-devel] [PATCH] util: remove the obsolete non-blocking connect Mao Zhongyi
2017-06-15  3:21 ` no-reply
2017-06-15  7:34 ` Juan Quintela [this message]
2017-06-15  7:56   ` Mao Zhongyi
2017-06-15  8:54 ` Daniel P. Berrange
2017-06-16  0:21 ` Fam Zheng
2017-06-16  5:43   ` Mao Zhongyi

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=87mv99aelr.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=jcody@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=maozy.fnst@cn.fujitsu.com \
    --cc=mitake.hitoshi@lab.ntt.co.jp \
    --cc=mreitz@redhat.com \
    --cc=namei.unix@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.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.