All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: lvs-users@linuxvirtualserver.org, lvs-devel@vger.kernel.org,
	horms@verge.net.au, jacky.hu@walmart.com, brouer@redhat.com,
	Jacky Hu <hengqing.hu@gmail.com>,
	jason.niesz@walmart.com
Subject: Re: [PATCH v8 0/2] Allow tunneling with gue encapsulation
Date: Tue, 2 Jul 2019 13:12:09 +0200	[thread overview]
Message-ID: <20190702131209.57c018ea@carbon> (raw)
In-Reply-To: <20190531084955.7cd4af00@carbon>

On Fri, 31 May 2019 08:49:55 +0200
Jesper Dangaard Brouer <brouer@redhat.com> wrote:

> On Thu, 30 May 2019 21:37:34 +0300 (EEST) Julian Anastasov <ja@ssi.bg> wrote:
> 
> > On Thu, 30 May 2019, Jacky Hu wrote:
> >   
> > > This patchset allows tunneling with gue encapsulation.
> > >   
> [...]
> > 
> > 	Both patches look ok to me, thanks!
> > 
> > Acked-by: Julian Anastasov <ja@ssi.bg>
> > 
> > 	Jesper, this patchset is based on the kernel patch
> > "[PATCH v4] ipvs: add checksum support for gue encapsulation"
> > which is to be applied to kernel trees. If needed, I can ping
> > you when the patch is accepted.  

Looks like this commit got applied to the kernel in commit 29930e314da3
("ipvs: add checksum support for gue encapsulation"), but only net-next.

Thus, I've applied this user-side patchset to ipvsadm.
 https://git.kernel.org/pub/scm/utils/kernel/ipvsadm/ipvsadm.git/

As you might have noticed, I've created a release v1.30 prio to applying
these.  As we have to wait for a kernel release, likely kernel v5.3,
before making an ipvsadm release with this GUE feature.

It should also make it easier for Julian's GRE work, to build on top.
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

commit 29930e314da3833437a2ddc7b17f6a954f38d8fb
Author: Jacky Hu <hengqing.hu@gmail.com>
Date:   Thu May 30 08:16:40 2019 +0800

    ipvs: add checksum support for gue encapsulation
    
    Add checksum support for gue encapsulation with the tun_flags parameter,
    which could be one of the values below:
    IP_VS_TUNNEL_ENCAP_FLAG_NOCSUM
    IP_VS_TUNNEL_ENCAP_FLAG_CSUM
    IP_VS_TUNNEL_ENCAP_FLAG_REMCSUM
    
    Signed-off-by: Jacky Hu <hengqing.hu@gmail.com>
    Signed-off-by: Julian Anastasov <ja@ssi.bg>
    Signed-off-by: Simon Horman <horms@verge.net.au>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

  parent reply	other threads:[~2019-07-02 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  8:00 [PATCH v8 0/2] Allow tunneling with gue encapsulation Jacky Hu
2019-05-30  8:00 ` [PATCH v8 1/2] ipvsadm: convert options to unsigned long long Jacky Hu
2019-05-30  8:00 ` [PATCH v8 2/2] ipvsadm: allow tunneling with gue encapsulation Jacky Hu
2019-05-30 18:37 ` [PATCH v8 0/2] Allow " Julian Anastasov
2019-05-31  6:49   ` Jesper Dangaard Brouer
2019-05-31  8:40     ` Bassem Mettichi
2019-07-02 11:12     ` Jesper Dangaard Brouer [this message]
2019-07-02 19:10       ` Julian Anastasov

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=20190702131209.57c018ea@carbon \
    --to=brouer@redhat.com \
    --cc=hengqing.hu@gmail.com \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=jacky.hu@walmart.com \
    --cc=jason.niesz@walmart.com \
    --cc=lvs-devel@vger.kernel.org \
    --cc=lvs-users@linuxvirtualserver.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.