From: "Julius Volz" <juliusv@google.com>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
Vince Busam <vbusam@google.com>,
wensong@linux-vs.org
Subject: Re: [rfc 0/3] IPVS: checksum updates
Date: Wed, 10 Sep 2008 19:30:52 +0200 [thread overview]
Message-ID: <f4845fc0809101030u2bd4dec4jb478ecc65240ea74@mail.gmail.com> (raw)
In-Reply-To: <20080909113131.GA3605@verge.net.au>
On Tue, Sep 9, 2008 at 1:31 PM, Simon Horman <horms@verge.net.au> wrote:
> On Tue, Sep 09, 2008 at 11:30:29AM +0200, Julius Volz wrote:
>> Great, thanks! I have tested TCP+UDP, local+remote clients, v4+v6,
>> NAT+DSR+TUN in all combinations that are expected to be working and
>> found no problems.
>
> Thanks once again for your testing. I'll send a pull request to Dave in
> the morning.
Thanks very much!
(CC: Wensong)
I guess it would make sense to start hosting the new ipvsadm version
somewhere on http://www.linuxvirtualserver.org/ soon. It could still
be marked as unstable and saying, "If you intend to use the
experimental IPv6 support for IPVS introduced in kernel 2.6.XX, you
will need this new version of ipvsadm: ...". Also, we can then point
to it in the Kconfig help text in CONFIG_IP_VS_IPV6. What do you
think?
Julius
--
Julius Volz - Corporate Operations - SysOps
Google Switzerland GmbH - Identification No.: CH-020.4.028.116-1
next prev parent reply other threads:[~2008-09-10 17:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 2:04 [rfc 0/3] IPVS: checksum updates Simon Horman
2008-09-08 2:04 ` [rfc 1/3] ipvs: handle PARTIAL_CHECKSUM Simon Horman
2008-09-08 7:24 ` Herbert Xu
2008-09-08 7:24 ` Herbert Xu
2008-09-08 9:05 ` Simon Horman
2008-09-08 9:54 ` Herbert Xu
2008-09-08 9:54 ` Herbert Xu
2008-09-08 2:04 ` [rfc 2/3] ipvs: Use inet_proto_csum_replace*() Simon Horman
2008-09-08 2:04 ` [rfc 3/3] ipvs: Consolidate checksuming code Simon Horman
2008-09-08 10:03 ` [rfc 0/3] IPVS: checksum updates Julius Volz
2008-09-08 10:41 ` Simon Horman
2008-09-08 11:42 ` Julius Volz
2008-09-08 11:57 ` Simon Horman
2008-09-08 12:04 ` Simon Horman
2008-09-08 12:14 ` Julius Volz
2008-09-08 12:34 ` Simon Horman
2008-09-08 13:12 ` Julius Volz
2008-09-08 13:20 ` Simon Horman
2008-09-08 13:42 ` Julius Volz
2008-09-08 15:32 ` Julius Volz
2008-09-08 23:22 ` Simon Horman
2008-09-08 23:40 ` Simon Horman
2008-09-09 9:30 ` Julius Volz
2008-09-09 11:31 ` Simon Horman
2008-09-10 17:30 ` Julius Volz [this message]
2008-09-10 23:29 ` Simon Horman
2008-09-11 13:07 ` Wensong Zhang
2008-09-11 13:45 ` Simon Horman
2008-09-11 13:55 ` Julius Volz
2008-09-11 14:43 ` Wensong Zhang
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=f4845fc0809101030u2bd4dec4jb478ecc65240ea74@mail.gmail.com \
--to=juliusv@google.com \
--cc=horms@verge.net.au \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vbusam@google.com \
--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.