From: Jiri Benc <jbenc@redhat.com>
To: "Du, Fan" <fan.du@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"mrjana@gmail.com" <mrjana@gmail.com>
Subject: Re: [Query] Delayed vxlan socket creation?
Date: Wed, 14 Dec 2016 10:29:31 +0100 [thread overview]
Message-ID: <20161214102931.307efe94@griffin> (raw)
In-Reply-To: <5A90DA2E42F8AE43BC4A093BF06788481A9457F1@SHSMSX103.ccr.corp.intel.com>
On Wed, 14 Dec 2016 07:49:24 +0000, Du, Fan wrote:
> I'm interested to one Docker issue[1] which looks like related to kernel vxlan socket creation
> as described in the thread. From my limited knowledge here, socket creation is synchronous ,
> and after the *socket* syscall, the sock handle will be valid and ready to linkup.
>
> Somehow I'm not sure the detailed scenario here, and which/how possible commit fix?
baf606d9c9b1^..56ef9c909b40
Jiri
next prev parent reply other threads:[~2016-12-14 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 7:49 [Query] Delayed vxlan socket creation? Du, Fan
2016-12-14 9:29 ` Jiri Benc [this message]
2016-12-15 8:41 ` Du, Fan
2016-12-14 17:24 ` Cong Wang
2016-12-15 8:43 ` Du, Fan
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=20161214102931.307efe94@griffin \
--to=jbenc@redhat.com \
--cc=fan.du@intel.com \
--cc=mrjana@gmail.com \
--cc=netdev@vger.kernel.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 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).