qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Eric Blake <eblake@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu v2] tap: Allow specifying a bridge
Date: Tue, 13 Sep 2016 17:39:33 +0200	[thread overview]
Message-ID: <20160913173933.4844ba9d@bahia> (raw)
In-Reply-To: <48ccbe12-9880-3ad7-92d9-d6a17b45b17b@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]

On Tue, 13 Sep 2016 09:49:09 -0500
Eric Blake <eblake@redhat.com> wrote:

> On 09/13/2016 02:11 AM, Alexey Kardashevskiy wrote:
> > The tap backend is already using qemu-bridge-helper to attach tap
> > interface to a bridge but (unlike the bridge backend) it always uses
> > the default bridge name - br0.
> > 
> > This adds a "br" property support to the tap backend.
> > 
> > Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> > --
> > Changes:
> > v2:
> > * documented a new member in json and hx
> > ---
> >  net/tap.c        |  4 +++-
> >  qapi-schema.json |  3 +++
> >  qemu-options.hx  | 12 +++++++-----
> >  3 files changed, 13 insertions(+), 6 deletions(-)
> >   
> 
> > +++ b/qapi-schema.json
> > @@ -2575,6 +2575,8 @@
> >  #
> >  # @downscript: #optional script to shut down the interface
> >  #
> > +# @br: #optional bridge name  
> 
> Missing a '(since 2.8)' designator.
> 
> Also, we don't have to abbreviate; 'bridge-name' may be easier to
> understand than 'br', as well as a mention of the default value if the
> parameter is not supplied.
> 

FWIW @br is consistent with what we already have in NetdevBridgeOptions
since 1.2.

> > +#
> >  # @helper: #optional command to execute to configure bridge
> >  #
> >  # @sndbuf: #optional send buffer limit. Understands [TGMKkb] suffixes.
> > @@ -2604,6 +2606,7 @@
> >      '*fds':        'str',
> >      '*script':     'str',
> >      '*downscript': 'str',
> > +    '*br':         'str',
> >      '*helper':     'str',
> >      '*sndbuf':     'size',
> >      '*vnet_hdr':   'bool',  
> 
> Oh, we already use underscore, so if you go with a longer name,
> 'bridge_name' would be more consistent than 'bridge-name', even though
> we prefer dash over underscore in new interfaces.
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-09-13 15:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  7:11 [Qemu-devel] [PATCH qemu v2] tap: Allow specifying a bridge Alexey Kardashevskiy
2016-09-13 14:49 ` Eric Blake
2016-09-13 15:39   ` Greg Kurz [this message]
2016-09-14  4:23     ` Alexey Kardashevskiy
2016-09-14 13:54       ` Eric Blake
2016-09-14 14:17 ` Greg Kurz
2016-09-14 15:12   ` Eric Blake
2016-09-22  7:03     ` Jason Wang
2016-09-14 21:04 ` Paolo Bonzini
2016-09-19  0:33   ` Alexey Kardashevskiy
2016-09-19 11:59     ` Paolo Bonzini
2016-09-22  7:05       ` Jason Wang

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=20160913173933.4844ba9d@bahia \
    --to=groug@kaod.org \
    --cc=aik@ozlabs.ru \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.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).