public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] kmalloc() vs. kmem_cache_alloc() for global TT?
Date: Tue, 24 May 2016 02:14:32 +0200	[thread overview]
Message-ID: <20160524001432.GD6623@otheros> (raw)
In-Reply-To: <20160514145129.GD4375@otheros>

Just to throw in some credibile sources.

https://static.lwn.net/images/pdf/LDD3/ch08.pdf:

"The main differences in passing from scull to scullc are a slight
speed improvement and better memory use. Since quanta are allocated
from a pool of memory fragments of exactly the right size, their
placement in memory is as dense as possible, as opposed to
scull quanta, which bring in an unpredictable memory fragmentation."


Also the paragraph regarding SLAB_HW_CACHE_ALIGN sounds
interesting. (And maybe it might be worth considering to ommit this
flag for the sake of our beloved but always memory deprived embedded
systems? Most TT entries aren't usually read anyway.)


Should we just go for kmem_cache_alloc() or should someone ask
on netdev@ first whether that chapter is still valid for current
kernels?

      parent reply	other threads:[~2016-05-24  0:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14 14:51 [B.A.T.M.A.N.] kmalloc() vs. kmem_cache_alloc() for global TT? Linus Lüssing
2016-05-14 14:54 ` Linus Lüssing
2016-05-15 11:27 ` Sven Eckelmann
2016-05-15 12:06   ` Linus Lüssing
2016-05-15 12:15     ` Sven Eckelmann
2016-05-15 12:17       ` Sven Eckelmann
2016-05-15 12:37       ` Linus Lüssing
2016-05-15 12:53         ` Sven Eckelmann
2016-05-15 12:41     ` Linus Lüssing
2016-05-15 20:50       ` Sven Eckelmann
2016-05-15 21:26         ` Linus Lüssing
2016-05-15 22:06           ` Sven Eckelmann
2016-05-24  0:14 ` Linus Lüssing [this message]

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=20160524001432.GD6623@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox