From: "David S. Miller" <davem@redhat.com>
To: Wensong Zhang <wensong@linux-vs.org>
Cc: ja@ssi.bg, netdev@oss.sgi.com
Subject: Re: [2.4/2.6] ipvs: improve conn rehashing, other fixes
Date: Mon, 22 Mar 2004 18:36:41 -0800 [thread overview]
Message-ID: <20040322183641.68ecb8a3.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0403230036130.3318-600000@penguin.linux-vs.org>
On Tue, 23 Mar 2004 00:58:38 +0800 (CST)
Wensong Zhang <wensong@linux-vs.org> wrote:
> Dave, please check the attached patches. There are three patches for 2.4,
> and two for 2.6.
I am going to apply everything except the ip_vs_ctl.c change as
Julian has tol me under seperate cover that the locking he adds
there is not really necessary.
Thanks.
next prev parent reply other threads:[~2004-03-23 2:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 18:46 [2.4/2.6] ipvs: improve conn rehashing, other fixes Julian Anastasov
2004-03-22 7:07 ` David S. Miller
2004-03-22 11:26 ` Julian Anastasov
2004-03-22 13:21 ` Wensong Zhang
2004-03-22 16:58 ` Wensong Zhang
2004-03-23 2:36 ` David S. Miller [this message]
2004-03-23 8:34 ` Julian Anastasov
2004-03-23 8:40 ` David S. Miller
2004-03-23 8:48 ` Julian Anastasov
2004-03-24 21:59 ` David S. Miller
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=20040322183641.68ecb8a3.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).