All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy King <acking@vmware.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: pv-drivers@vmware.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	gregkh@linuxfoundation.org, davem@davemloft.net,
	George Zhang <georgezhang@vmware.com>
Subject: Re: [Pv-drivers] [PATCH 0/6] VSOCK for Linux upstreaming
Date: Wed, 14 Nov 2012 08:42:44 -0800 (PST)	[thread overview]
Message-ID: <1636188668.22560872.1352911364387.JavaMail.root@vmware.com> (raw)
In-Reply-To: <50A01FB1.1080502@gmail.com>

Hi Sasha,

Thanks for taking a look.

> So all the documentation I see in the VMCI Socket Programming Guide
> is about userspace programming, and the documentation in af_vsock.c
> is all around implementation considerations.

Agreed, we're sorely lacking in proper documentation for the internal
protocol.  We're in the process of writing such a specification and
will post it to LKML next week at the latest.

> example, whats the deal with REQUEST/REQUEST2? it appears like
> something to deal with legacy code, but I'd really like to have it
> documented somewhere instead of trying to figure how everything

Correct, we have a legacy protocol and a v2, the latter now being
the default.  This particular packet is sent by the client when
initiating a STREAM connection.  The sequence is REQUEST(2)->
NEGOTIATE(2)->OFFER->ACCEPT.  It will be properly documented in
the specification we post next week.

Thanks!
- Andy

  reply	other threads:[~2012-11-14 16:42 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 18:00 [PATCH 0/6] VSOCK for Linux upstreaming George Zhang
2012-11-05 18:00 ` [PATCH 1/6] VSOCK: vsock protocol implementation George Zhang
2012-11-06  9:10   ` Stephen Hemminger
2012-11-06  9:10     ` Stephen Hemminger
2012-11-06 14:31     ` [Pv-drivers] " Andy King
2012-11-05 18:01 ` [PATCH 2/6] VSOCK: vsock address implementaion George Zhang
2012-11-05 18:01 ` [PATCH 3/6] VSOCK: notification implementation George Zhang
2012-11-05 18:01 ` [PATCH 4/6] VSOCK: statistics implementation George Zhang
2012-11-05 18:01 ` [PATCH 5/6] VSOCK: utility functions George Zhang
2012-11-05 18:01 ` George Zhang
2012-11-05 18:01 ` [PATCH 6/6] VSOCK: header and config files George Zhang
2012-11-05 18:09 ` [PATCH 0/6] VSOCK for Linux upstreaming David Miller
2012-11-05 18:09   ` David Miller
2012-11-05 18:10   ` David Miller
2012-11-05 18:10     ` David Miller
2012-11-05 18:24     ` George Zhang
2012-11-05 18:24       ` George Zhang
2012-11-05 18:19   ` [Pv-drivers] " Andy King
2012-11-07  6:58     ` Gerd Hoffmann
2012-11-07  6:58       ` Gerd Hoffmann
2012-11-08 15:47       ` Andy King
2012-11-08 15:47         ` Andy King
2012-11-15 21:32       ` Anthony Liguori
2012-11-15 21:32       ` Anthony Liguori
2012-11-19  9:59         ` Benjamin Herrenschmidt
2012-11-19  9:59         ` Benjamin Herrenschmidt
2012-12-06 15:28         ` Andy King
2012-12-06 15:28           ` Andy King
2012-11-05 18:23 ` Sasha Levin
2012-11-05 18:23   ` Sasha Levin
2012-11-05 18:32   ` George Zhang
2012-11-05 18:32     ` George Zhang
2012-11-11 21:59     ` Sasha Levin
2012-11-11 21:59       ` Sasha Levin
2012-11-14 16:42       ` Andy King [this message]
2012-11-06  9:00 ` Stephen Hemminger
2012-11-06  9:00   ` Stephen Hemminger
2012-11-06  9:06   ` Stephen Hemminger
2012-11-06  9:06     ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2013-01-08 23:59 George Zhang
2013-01-09  0:21 ` Greg KH
2013-01-09  1:30   ` David Miller
2013-01-09  1:41     ` [Pv-drivers] " Dmitry Torokhov
2013-01-09  1:41       ` Dmitry Torokhov
2013-01-09  1:46       ` David Miller
2013-01-09  1:46         ` David Miller
2013-01-09  2:22         ` Dmitry Torokhov
2013-01-09  2:22           ` Dmitry Torokhov
2013-01-09  8:10           ` Gerd Hoffmann
2013-01-09  8:10             ` Gerd Hoffmann
2013-01-10  2:42             ` Andy King
2013-01-10  2:42               ` Andy King
2013-01-25 21:33               ` Andy King
2013-01-25 21:33               ` Andy King
2013-02-05  4:42         ` Andy King
2013-02-05  4:42           ` Andy King

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=1636188668.22560872.1352911364387.JavaMail.root@vmware.com \
    --to=acking@vmware.com \
    --cc=davem@davemloft.net \
    --cc=georgezhang@vmware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    --cc=virtualization@lists.linux-foundation.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.