All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: David Miller <davem@davemloft.net>
Cc: heder@google.com, netdev@vger.kernel.org, eric.dumazet@gmail.com,
	lvs-users@linuxvirtualserver.org, malcolm@loadbalancer.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] IPVS: logging sizeof(struct ip_vs_conn) on startup
Date: Tue, 28 Jul 2009 10:19:27 +1000	[thread overview]
Message-ID: <20090728001926.GA20230@verge.net.au> (raw)
In-Reply-To: <20090727.114845.177925839.davem@davemloft.net>

On Mon, Jul 27, 2009 at 11:48:45AM -0700, David Miller wrote:
> From: Hannes Eder <heder@google.com>
> Date: Mon, 27 Jul 2009 15:13:57 +0200
> 
> > No more guessing, how much memory used by IPVS for a connection.
> > 
> > [ The number printed is a lower bound, as ip_vs_conn_cache uses
> > SLAB_HWCACHE_ALIGN. ]
> > 
> > Signed-off-by: Hannes Eder <heder@google.com>
> > Signed-off-by: Simon Horman <horms@verge.net.au>
> 
> Who needs to know this?  A developer?
> 
> They can run tools such as 'pahole' et al. to fish out this
> information even when only a kernel binary is available.
> 
> For the user, it's just noise.
> 
> I'm not applying this, sorry.

Surprisingly its a very common question amongst users,
because they want to know how much memory they need.
It is of course all a bit silly, because the amount of
memory used by the connection table is usually very small,
but people still ask.


  reply	other threads:[~2009-07-28  0:19 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
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 [this message]
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=20090728001926.GA20230@verge.net.au \
    --to=horms@verge.net.au \
    --cc=davem@davemloft.net \
    --cc=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 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.