All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH v2] batman-adv: use kmem_cache for translation table
Date: Tue, 28 Jun 2016 17:40:34 +0200	[thread overview]
Message-ID: <20160628154034.GG3221@otheros> (raw)
In-Reply-To: <8290095.7NSUu8plcS@sven-edge>

On Mon, Jun 27, 2016 at 08:09:58AM +0200, Sven Eckelmann wrote:
> On Monday 27 June 2016 06:02:18 Linus Lüssing wrote:
> [...]
> > Looks good. Do you have any typical numbers regarding tt_change_cache
> > and tt_req_cache sizes for specific setups?
> 
> No, I don't have any numbers.

Freifunk Rhein-Neckar at about 4pm (~700 nodes, ~1800 clients, batman-adv compat15):

-----
batadv_tt_roam_cache      0      0     64   63    1 : tunables  120   60    8 : slabdata      0      0      0
batadv_tt_req_cache      1     63     64   63    1 : tunables  120   60    8 : slabdata      1      1      0
batadv_tt_change_cache      0      0     32  124    1 : tunables  120   60    8 : slabdata      0      0      0
batadv_tt_orig_cache   3210   3213     64   63    1 : tunables  120   60    8 : slabdata     51     51      0
batadv_tg_cache     3162   3162    128   31    1 : tunables  120   60    8 : slabdata    102    102      0
batadv_tl_cache        2     31    128   31    1 : tunables  120   60    8 : slabdata      1      1      0
-----

-> snapshot taken from an x86 machine connected to a Gluon ar71xx node.

So the roam, req, change and tl cache are mostly empty here. On the other hand, they could
probably gain a significant size once a larger LAN gets bridged to bat0, I guess.
Also looks like various file systems have about half a dozen caches each with most
of them being quite empty most of the time.

So, I guess it's ok to have the roam/req/change/tl caches.


Not sure whether I should (since TT is Antonio's part) but the patch looks
correct, the previous version with the same concept tested and looks very
similar to what I had incidentally been coding at the same time as Sven :), so:

Acked-by: Linus Lüssing <linus.luessing@c0d3.blue>

  reply	other threads:[~2016-06-28 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-25 14:44 [B.A.T.M.A.N.] [PATCH v2] batman-adv: use kmem_cache for translation table Sven Eckelmann
2016-06-25 15:46 ` Sven Eckelmann
2016-06-27  4:02   ` Linus Lüssing
2016-06-27  6:09     ` Sven Eckelmann
2016-06-28 15:40       ` Linus Lüssing [this message]
2016-07-08  9:53 ` Marek Lindner

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=20160628154034.GG3221@otheros \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.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.