From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Simon Horman <horms@verge.net.au>
Cc: Julian Anastasov <ja@ssi.bg>, lvs-devel@vger.kernel.org
Subject: Re: [PATCH v4 0/8] Changes for IPVS sync
Date: Wed, 2 May 2012 02:36:28 +0200 [thread overview]
Message-ID: <20120502003628.GA14990@1984> (raw)
In-Reply-To: <20120426062047.GE13141@verge.net.au>
Hi Simon,
On Thu, Apr 26, 2012 at 03:20:47PM +0900, Simon Horman wrote:
> On Tue, Apr 24, 2012 at 11:46:34PM +0300, Julian Anastasov wrote:
> > The following patchset contains changes for the
> > master-backup synchronization mechanism.
>
> Thanks.
>
> I have pushed these to ipvs-next. But I am awaiting Pablo's review
> before sending him a pull request.
Please, go ahead with that pull request.
I wanted to sort out 3.4-rc things first before looking again at
net-next stuff.
Better one thing at a time.
prev parent reply other threads:[~2012-05-02 0:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 20:46 [PATCH v4 0/8] Changes for IPVS sync Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 1/8] ipvs: ignore IP_VS_CONN_F_NOOUTPUT in backup server Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 2/8] ipvs: remove check for IP_VS_CONN_F_SYNC from ip_vs_bind_dest Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 3/8] ipvs: fix ip_vs_try_bind_dest to rebind app and transmitter Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 4/8] ipvs: always update some of the flags bits in backup Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 5/8] ipvs: wakeup master thread Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 6/8] ipvs: reduce sync rate with time thresholds Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 7/8] ipvs: add support for sync threads Julian Anastasov
2012-04-24 20:46 ` [PATCH v4 8/8] ipvs: optimize the use of flags in ip_vs_bind_dest Julian Anastasov
2012-04-26 6:20 ` [PATCH v4 0/8] Changes for IPVS sync Simon Horman
2012-05-02 0:36 ` Pablo Neira Ayuso [this message]
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=20120502003628.GA14990@1984 \
--to=pablo@netfilter.org \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.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.