From: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
To: Eric Blake <eblake@redhat.com>
Cc: Anton Ivanov <antivano@cisco.com>,
pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] net: L2TPv3 transport
Date: Mon, 10 Mar 2014 16:31:38 +0000 [thread overview]
Message-ID: <531DE8EA.3000100@kot-begemot.co.uk> (raw)
In-Reply-To: <531DE2EA.8000101@redhat.com>
On 10/03/14 16:06, Eric Blake wrote:
> On 03/10/2014 05:31 AM, anton.ivanov@kot-begemot.co.uk wrote:
>> From: Anton Ivanov <antivano@cisco.com>
> When sending revisions of a patch sent earlier, be sure to include
> 'PATCHv2' (or higher, as appropriate) in the subject,...
OK.
>
>> This tranport allows to connect a qemu nic to a static Ethernet
>> over L2TPv3 tunnel. The transport supports all options present
>> in the linux kernel implementation. It allows qemu to connect
>> to any linux host running kernel 3.3+, most routers and network
>>
>> Signed-off-by: Anton Ivanov <antivano@cisco.com>
>> ---
> ...and describe what changed from v1 after the --- separator. That way,
> earlier reviewers will know what differences to look for, instead of
> assuming it is a brand new patch.
OK.
This takes into account everything discussed so far except passing 0
instead of PROTO_L2TPV3 to getaddrinfo. That approach unfortunately does
not work.
The .hx now includes an example versus Linux kernel which ends up being
included in the man pages as well as the help text.
I believe we are down to 1-2 issues - the few remaining omissions you
noticed on the interface and what to do with the socket() args and
PROTO_L2TPV3.
>
>> +++ b/qapi-schema.json
>> @@ -2940,6 +2940,60 @@
>> '*localaddr': 'str',
>> '*udp': 'str' } }
>>
>> +# @NetdevL2TPv3Options
> Missing a ## line prior to the struct name.
OK.
>
>> +# @pincounter: #optional pin sequence counter to zero - workaround for buggy implementations or networks with packet reorder
> Super long line. Please wrap at 80 columns.
OK.
>
>> +#
>> +# @txcookie: #optional 32 or 64 bit transmit cookie
>> +#
>> +# @rxcookie: #optional 32 or 64 bit receive cookie
>> +#
>> +# @txsession: 32 bit transmit session
>> +#
>> +# @rxsession: 32 bit receive session - if not specified set to the same value as transmit
>> +#
>> +# @optional: additional offset - allows the insertion of additional application-specific data before the packet payload
> Another long line. Also, you don't have a variable named 'optional';
> you probably meant '@offset: #optional'.
I thought I fixed that... Guess I did not...
Thanks,
A.
>
prev parent reply other threads:[~2014-03-10 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 11:31 [Qemu-devel] [PATCH] net: L2TPv3 transport anton.ivanov
2014-03-10 15:05 ` Stefan Hajnoczi
2014-03-10 15:09 ` Anton Ivanov (antivano)
2014-03-10 16:06 ` Eric Blake
2014-03-10 16:31 ` Anton Ivanov [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=531DE8EA.3000100@kot-begemot.co.uk \
--to=anton.ivanov@kot-begemot.co.uk \
--cc=afaerber@suse.de \
--cc=antivano@cisco.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--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).