All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Julian Anastasov <ja@ssi.bg>
Cc: Simon Horman <horms@verge.net.au>,
	lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org,
	Wensong Zhang <wensong@linux-vs.org>
Subject: Re: [GIT PULL nf-next 00/21] Second Round of IPVS Updates for v3.18
Date: Wed, 17 Sep 2014 10:30:41 +0200	[thread overview]
Message-ID: <20140917083041.GA4762@salvia> (raw)
In-Reply-To: <alpine.LFD.2.11.1409170013440.3254@ja.home.ssi.bg>

On Wed, Sep 17, 2014 at 12:27:03AM +0300, Julian Anastasov wrote:
> 
> 	Hello,
> 
> On Tue, 16 Sep 2014, Pablo Neira Ayuso wrote:
> 
> > Hi Simon,
> > 
> > On Tue, Sep 16, 2014 at 09:34:14AM +0900, Simon Horman wrote:
> > > Hi Pablo,
> > > 
> > > please consider these IPVS updates for v3.18.
> > > 
> > > * Add simple weighted failover scheduler
> > >   - Thanks to Kenny Mathis
> > > * Support v6 real servers in v4 pools and vice versa
> > >   - Thanks to Alex Gartrell and Julian Anastasov
> > 
> > I need a slightly larger description of this series.
> > 
> > I think you can merge patches 13-19 too. They are mostly two liners
> > with a similar description, so they naturally belong to the same
> > logical change. I would like to reduce the patchbomb pull request for
> > David.
> 
> 	Good idea, done.
> 
> 	Simon, I'm attaching such patch that replaces all
> these "ipvs: use correct address family in * logs".
> It additionally changes the new ip_vs_fo.c scheduler
> and ip_vs_wrr.c which was missed.

Thanks Julian.

@Simon, I can manually apply this batch if that reduces your workload.
Please let me know what you prefer.

Still I'd really appreciate a longer series description that I can
include in the pull-request for David.

Thanks.

  reply	other threads:[~2014-09-17  8:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  0:34 [GIT PULL nf-next 00/21] Second Round of IPVS Updates for v3.18 Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 01/21] ipvs: Add simple weighted failover scheduler Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 02/21] ipvs: Add destination address family to netlink interface Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 03/21] ipvs: Supply destination addr family to ip_vs_{lookup_dest,find_dest} Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 04/21] ipvs: Pass destination address family to ip_vs_trash_get_dest Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 05/21] ipvs: Supply destination address family to ip_vs_conn_new Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 06/21] ipvs: prevent mixing heterogeneous pools and synchronization Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 07/21] ipvs: Pull out crosses_local_route_boundary logic Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 08/21] ipvs: Pull out update_pmtu code Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 09/21] ipvs: Add generic ensure_mtu_is_adequate to handle mixed pools Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 10/21] ipvs: support ipv4 in ipv6 and ipv6 in ipv4 tunnel forwarding Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 11/21] ipvs: address family of LBLC entry depends on svc family Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 12/21] ipvs: address family of LBLCR " Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 13/21] ipvs: use correct address family in DH logs Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 14/21] ipvs: use correct address family in LC logs Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 15/21] ipvs: use correct address family in NQ logs Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 16/21] ipvs: use correct address family in RR logs Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 17/21] ipvs: use correct address family in SED logs Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 18/21] ipvs: use correct address family in SH logs Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 19/21] ipvs: use correct address family in WLC logs Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 20/21] ipvs: use the new dest addr family field Simon Horman
2014-09-16  0:34 ` [PATCH nf-next 21/21] ipvs: Allow heterogeneous pools now that we support them Simon Horman
2014-09-16 17:25 ` [GIT PULL nf-next 00/21] Second Round of IPVS Updates for v3.18 Pablo Neira Ayuso
2014-09-16 21:27   ` Julian Anastasov
2014-09-17  8:30     ` Pablo Neira Ayuso [this message]
2014-09-17 23:56       ` Simon Horman
2014-09-18  0:27         ` Simon Horman

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=20140917083041.GA4762@salvia \
    --to=pablo@netfilter.org \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-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.