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.] kmalloc() vs. kmem_cache_alloc() for global TT?
Date: Sun, 15 May 2016 14:37:33 +0200 [thread overview]
Message-ID: <20160515123733.GH4375@otheros> (raw)
In-Reply-To: <22866212.dooYpi8Uhz@sven-edge>
On Sun, May 15, 2016 at 02:15:01PM +0200, Sven Eckelmann wrote:
> On Sunday 15 May 2016 14:06:26 Linus Lüssing wrote:
> [...]
> > [0]
> > https://git.open-mesh.org/batman-adv.git/shortlog/refs/heads/linus/kmem-cac
> > he
>
> This patchset has a bad bug. It still uses kfree for tt_local objects
> allocated via kmem_cache_(z)alloc.
Where?
next prev parent reply other threads:[~2016-05-15 12:37 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 [this message]
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
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=20160515123733.GH4375@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.