qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang, Chen" <chen.zhang@intel.com>
To: Jason Wang <jasowang@redhat.com>,
	qemu-dev <qemu-devel@nongnu.org>,
	"Eric Blake" <eblake@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: Zhang Chen <zhangckid@gmail.com>
Subject: RE: [PATCH 1/3] qapi/net: Add new QMP command for COLO passthrough
Date: Tue, 5 Jan 2021 03:28:45 +0000	[thread overview]
Message-ID: <666f41843baf4c84bbafa7f9fdfba96f@intel.com> (raw)
In-Reply-To: <05999128-75c0-aeaf-255f-8c1ec7699eab@redhat.com>



> -----Original Message-----
> From: Jason Wang <jasowang@redhat.com>
> Sent: Wednesday, December 30, 2020 11:57 AM
> To: Zhang, Chen <chen.zhang@intel.com>; qemu-dev <qemu-
> devel@nongnu.org>; Eric Blake <eblake@redhat.com>; Dr. David Alan
> Gilbert <dgilbert@redhat.com>; Markus Armbruster <armbru@redhat.com>
> Cc: Zhang Chen <zhangckid@gmail.com>
> Subject: Re: [PATCH 1/3] qapi/net: Add new QMP command for COLO
> passthrough
> 
> 
> On 2020/12/29 上午10:56, Zhang, Chen wrote:
> >> I think we can start form COLO. To avoid QMP compatibility issues, I
> >> would like to add the n tuple and wildcard support now.
> > OK, I will do this job in next version.
> > For the QMP compatibility issues, please give me a demo of what we want
> to see, Like some existing commands.
> 
> 
> I meant if we start from port and then want to add e.g n-tuple support.
> Do we need to introduce another command? Or is there any introspection
> that can let management layer know about this?

OK, I will add the n-tuple support.
It looks basic command are add/del connection, Do you think something needs to be introduced?
For the management layer, I don't know the detail process of how to add new Qemu command support for example libvirt.
Maybe depend on libvirt community's plan?

Thanks
Chen 

> 
> Thanks
> 
> 
> >
> > Thanks
> > Chen
> >


  reply	other threads:[~2021-01-05  3:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  1:09 [PATCH 0/3] Bypass specific network traffic in COLO Zhang Chen
2020-12-24  1:09 ` [PATCH 1/3] qapi/net: Add new QMP command for COLO passthrough Zhang Chen
2020-12-25  6:20   ` Jason Wang
2020-12-28  0:38     ` Zhang, Chen
2020-12-28  7:11       ` Jason Wang
2020-12-29  2:56         ` Zhang, Chen
2020-12-30  3:56           ` Jason Wang
2021-01-05  3:28             ` Zhang, Chen [this message]
2021-01-05  4:17               ` Jason Wang
2021-01-05  6:29                 ` Zhang, Chen
2021-01-19 19:32   ` Eric Blake
2021-01-21  1:50     ` Zhang, Chen
2020-12-24  1:09 ` [PATCH 2/3] hmp-commands: Add new HMP " Zhang Chen
2020-12-24  1:09 ` [PATCH 3/3] net/colo-compare: Add handler for passthrough connection Zhang Chen
2021-01-14 13:45   ` Lukas Straub
2021-01-15  9:07     ` Zhang, Chen
2021-01-15 16:06       ` Lukas Straub
2021-01-14 13:50   ` Lukas Straub
2021-01-15  9:08     ` Zhang, Chen
2020-12-25  6:23 ` [PATCH 0/3] Bypass specific network traffic in COLO Jason Wang
2020-12-28  0:38   ` Zhang, Chen
2021-01-04 13:06 ` Dr. David Alan Gilbert
2021-01-05  3:28   ` Zhang, Chen

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=666f41843baf4c84bbafa7f9fdfba96f@intel.com \
    --to=chen.zhang@intel.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhangckid@gmail.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).