All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Hans Schillstrom <hans.schillstrom@ericsson.com>
Cc: Julian Anastasov <ja@ssi.bg>,
	LVS-Devel <lvs-devel@vger.kernel.org>,
	"wensong@linux-vs.org" <wensong@linux-vs.org>,
	Daniel Lezcano <daniel.lezcano@free.fr>,
	hans@schillstrom.com
Subject: Re: [*v5 PATCH 0/7] IPVS: Backup Adding Ipv6 and Persistence support
Date: Wed, 17 Nov 2010 06:48:43 +0900	[thread overview]
Message-ID: <20101116214843.GE2647@verge.net.au> (raw)
In-Reply-To: <201011162032.10807.hans.schillstrom@ericsson.com>

On Tue, Nov 16, 2010 at 08:32:10PM +0100, Hans Schillstrom wrote:
> This patch series adds/(updates) the following functionality
> in the synchronization between master and backup daemons.
> 
>  - IPv6
>  - Persistence Engine
>  - Firewall marks transferred
>  - Time-outs transferred.
>  - Flag field increased to 32 bits.
> 
> Note:
> This patch set is build upon lvs-next-2.6
> i.e. last patch in master was "ipvs: allow transmit of GRO aggregated skbs"

Hi Hans,

thanks. I can apply the patches cleanly this time.
Sorry about yesterday's mess.

I have looked over the patches and they seem good to me.
Julian, can you ack the patches that you are ok with pushing?
Perhaps all of them?

Also, some of the changes look like they might be stable material.
Especially "IPVS: Split ports[3] into src_port and dst_port" and
"IPVS: skb defrag in L7 helpers". Any thoughts?


  parent reply	other threads:[~2010-11-16 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 19:32 [*v5 PATCH 0/7] IPVS: Backup Adding Ipv6 and Persistence support Hans Schillstrom
2010-11-16 21:17 ` Julian Anastasov
2010-11-16 21:48 ` Simon Horman [this message]
2010-11-16 22:40   ` 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=20101116214843.GE2647@verge.net.au \
    --to=horms@verge.net.au \
    --cc=daniel.lezcano@free.fr \
    --cc=hans.schillstrom@ericsson.com \
    --cc=hans@schillstrom.com \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --cc=wensong@linux-vs.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.