From: Eric Dumazet <eric.dumazet@gmail.com>
To: Hannes Eder <heder@google.com>
Cc: netdev@vger.kernel.org, lvs-users@linuxvirtualserver.org,
malcolm@loadbalancer.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IPVS: logging sizeof(struct ip_vs_conn) on startup
Date: Mon, 27 Jul 2009 11:25:25 +0200 [thread overview]
Message-ID: <4A6D7285.9080909@gmail.com> (raw)
In-Reply-To: <20090727090741.16509.35291.stgit@jazzy.zrh.corp.google.com>
Hannes Eder a écrit :
> No more guessing, how much memory is used by IPVS for a connection.
>
> Signed-off-by: Hannes Eder <heder@google.com>
> ---
> net/netfilter/ipvs/ip_vs_core.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/net/netfilter/ipvs/ip_vs_core.c b/net/netfilter/ipvs/ip_vs_core.c
> index b021464..5b0997c 100644
> --- a/net/netfilter/ipvs/ip_vs_core.c
> +++ b/net/netfilter/ipvs/ip_vs_core.c
> @@ -1475,7 +1475,8 @@ static int __init ip_vs_init(void)
> goto cleanup_conn;
> }
>
> - IP_VS_INFO("ipvs loaded.\n");
> + IP_VS_INFO("ipvs loaded (using %Zd bytes/connection).\n",
> + sizeof(struct ip_vs_conn));
> return ret;
>
> cleanup_conn:
Well, ip_vs_conn_cache uses SLAB_HWCACHE_ALIGN, so this should be rounded up
to L1 cache size. Or add "at least" like in line 1080
of net/netfilter/ipvs/ip_vs_conn.c :
IP_VS_DBG(0, "Each connection entry needs %Zd bytes at least\n",
sizeof(struct ip_vs_conn));
next prev parent reply other threads:[~2009-07-27 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 9:08 [PATCH] IPVS: logging sizeof(struct ip_vs_conn) on startup Hannes Eder
2009-07-27 9:22 ` Simon Horman
2009-07-27 9:25 ` Eric Dumazet [this message]
2009-07-27 10:34 ` Hannes Eder
2009-07-27 13:13 ` [PATCH v2] " Hannes Eder
2009-07-27 18:48 ` David Miller
2009-07-28 0:19 ` Simon Horman
2009-07-28 5:38 ` Eric Dumazet
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=4A6D7285.9080909@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=heder@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-users@linuxvirtualserver.org \
--cc=malcolm@loadbalancer.org \
--cc=netdev@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 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).