netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
To: "sgarzare@redhat.com" <sgarzare@redhat.com>
Cc: "stefanha@redhat.com" <stefanha@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH v3 0/2] Enhance virtio-vsock connection semantics
Date: Fri, 14 Feb 2020 12:20:25 +0000	[thread overview]
Message-ID: <cdad5dee6207d8fdb667cbdc4b67d8f9b61ad23c.camel@intel.com> (raw)
In-Reply-To: <20200214121803.kpblkpywkvwkoc7h@steredhat>

On Fri, 2020-02-14 at 13:18 +0100, Stefano Garzarella wrote:
> On Fri, Feb 14, 2020 at 12:48:00PM +0100, Sebastien Boeuf wrote:
> > This series improves the semantics behind the way virtio-vsock
> > server
> > accepts connections coming from the client. Whenever the server
> > receives a connection request from the client, if it is bound to
> > the
> > socket but not yet listening, it will answer with a RST packet. The
> > point is to ensure each request from the client is quickly
> > processed
> > so that the client can decide about the strategy of retrying or
> > not.
> > 
> > The series includes along with the improvement patch a new test to
> > ensure the behavior is consistent across all hypervisors drivers.
> > 
> > Sebastien Boeuf (2):
> >   net: virtio_vsock: Enhance connection semantics
> >   tools: testing: vsock: Test when server is bound but not
> > listening
> > 
> >  net/vmw_vsock/virtio_transport_common.c |  1 +
> >  tools/testing/vsock/vsock_test.c        | 77
> > +++++++++++++++++++++++++
> >  2 files changed, 78 insertions(+)
> > 
> 
> Thanks,
> now they apply cleanly!

Great!

> 
> Tested-by: Stefano Garzarella <sgarzare@redhat.com>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
> 
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  reply	other threads:[~2020-02-14 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 11:48 [PATCH v3 0/2] Enhance virtio-vsock connection semantics Sebastien Boeuf
2020-02-14 11:48 ` [PATCH v3 1/2] net: virtio_vsock: Enhance " Sebastien Boeuf
2020-02-14 11:48 ` [PATCH v3 2/2] tools: testing: vsock: Test when server is bound but not listening Sebastien Boeuf
2020-02-14 12:18 ` [PATCH v3 0/2] Enhance virtio-vsock connection semantics Stefano Garzarella
2020-02-14 12:20   ` Boeuf, Sebastien [this message]
2020-02-17  3:02 ` David Miller
2020-02-17  7:43   ` Boeuf, Sebastien

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=cdad5dee6207d8fdb667cbdc4b67d8f9b61ad23c.camel@intel.com \
    --to=sebastien.boeuf@intel.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --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).