From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: horms@verge.net.au, lvs-devel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
wensong@linux-vs.org, ja@ssi.bg, hans.schillstrom@ericsson.com,
brouer@redhat.com
Subject: Re: [PATCH 18/18] export sysctl symbols needed by ip_vs_sync
Date: Sun, 06 May 2012 17:19:38 -0400 (EDT) [thread overview]
Message-ID: <20120506.171938.850582286130598907.davem@davemloft.net> (raw)
In-Reply-To: <20120506205412.GA22406@1984>
From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Sun, 6 May 2012 22:54:12 +0200
> Hi David,
>
> The IPVS people needs this patch for net-next to allow to tune the
> socket buffer for ipvs_sync (the state synchronization that they do
> from kernel-space). This exports sysctl_wmem_max and sysctl_rmem_max
> living in net/core/sock.c. So far, they've been using global socket
> tuning to make them bigger (this avoids overruning the socket under
> high peak of state-change synchronization).
>
> I think this is out of my scope (since it's out of the netfilter
> tree).
>
> Would you acknowledge it, please?
Feel free to merge it via your tree:
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2012-05-06 21:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 6:22 [GIT PULL net-next v2] IPVS Simon Horman
2012-05-02 6:22 ` [PATCH 01/18] ipvs: timeout tables do not need GFP_ATOMIC allocation Simon Horman
2012-05-02 6:22 ` [PATCH 02/18] ipvs: LBLC scheduler does not need GFP_ATOMIC allocation on init Simon Horman
2012-05-02 6:22 ` [PATCH 03/18] ipvs: DH scheduler does not need GFP_ATOMIC allocation Simon Horman
2012-05-02 6:22 ` [PATCH 04/18] ipvs: WRR " Simon Horman
2012-05-02 6:22 ` [PATCH 05/18] ipvs: LBLCR scheduler does not need GFP_ATOMIC allocation on init Simon Horman
2012-05-02 6:22 ` [PATCH 06/18] ipvs: SH scheduler does not need GFP_ATOMIC allocation Simon Horman
2012-05-02 6:22 ` [PATCH 07/18] netfilter: ipvs: use GFP_KERNEL allocation where possible Simon Horman
2012-05-02 6:22 ` [PATCH 08/18] ipvs: ignore IP_VS_CONN_F_NOOUTPUT in backup server Simon Horman
2012-05-02 6:22 ` [PATCH 09/18] ipvs: remove check for IP_VS_CONN_F_SYNC from ip_vs_bind_dest Simon Horman
2012-05-02 6:22 ` [PATCH 10/18] ipvs: fix ip_vs_try_bind_dest to rebind app and transmitter Simon Horman
2012-05-02 6:22 ` [PATCH 11/18] ipvs: always update some of the flags bits in backup Simon Horman
2012-05-02 6:22 ` [PATCH 12/18] ipvs: wakeup master thread Simon Horman
2012-05-02 6:22 ` [PATCH 13/18] ipvs: reduce sync rate with time thresholds Simon Horman
2012-05-02 6:22 ` [PATCH 14/18] ipvs: add support for sync threads Simon Horman
2012-05-02 6:22 ` [PATCH 15/18] ipvs: optimize the use of flags in ip_vs_bind_dest Simon Horman
2012-05-02 6:22 ` [PATCH 16/18] IPVS: ip_vs_ftp.c: local functions should not be exposed globally Simon Horman
2012-05-02 6:22 ` [PATCH 17/18] IPVS: ip_vs_proto.c: " Simon Horman
2012-05-02 6:22 ` [PATCH 18/18] export sysctl symbols needed by ip_vs_sync Simon Horman
2012-05-06 20:54 ` Pablo Neira Ayuso
2012-05-06 21:19 ` David Miller [this message]
2012-05-06 21:56 ` [GIT PULL net-next v2] IPVS Pablo Neira Ayuso
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=20120506.171938.850582286130598907.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=hans.schillstrom@ericsson.com \
--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=pablo@netfilter.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 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).