All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: anton.ivanov@cambridgegreys.com
Cc: qemu-devel@nongnu.org, jasowang@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Unified Socket Transport
Date: Tue, 18 Jul 2017 08:27:13 +0100	[thread overview]
Message-ID: <20170718072713.GC11927@redhat.com> (raw)
In-Reply-To: <20170718060627.2107-1-anton.ivanov@cambridgegreys.com>

On Tue, Jul 18, 2017 at 07:06:27AM +0100, anton.ivanov@cambridgegreys.com wrote:
> From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
> 
> 1. Creates a common recvmmsg backend for socket transports
> 2. Migrates L2TPv3 to the new backend
> 3. Adds gre socket transport - a vm can attach directly to GRE
> 4. Adds raw socket transport - a vm can attach directly to an
> Ethernet interface
> 5. Adds simplistic static VXLAN tunnel transport (no
> control plane).
> 6. Sets up some of the infrastructure for future addition of
> sendmmsg

This list of features is a really strong sign that you should split
this patch up into a patch series with multiple commits, each commit
adding / changing a single feature. Especially keep refactoring of
existing code completely separate from adding of new features.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  parent reply	other threads:[~2017-07-18  7:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18  6:06 [Qemu-devel] [PATCH] Unified Socket Transport anton.ivanov
2017-07-18  6:11 ` no-reply
2017-07-18  6:12 ` no-reply
2017-07-18  6:58   ` Anton Ivanov
2017-07-18  6:18 ` Anton Ivanov
2017-07-18  7:27 ` Daniel P. Berrange [this message]
2017-07-18  7:44   ` Anton Ivanov
2017-07-18 11:49 ` no-reply

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=20170718072713.GC11927@redhat.com \
    --to=berrange@redhat.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=jasowang@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 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.