From: Antony Pavlov <antonynpavlov@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>, "Серафим Долбилов" <s.dlblv@ya.ru>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [HELP] Barebox porting
Date: Wed, 16 Jan 2019 21:48:37 +0300 [thread overview]
Message-ID: <20190116214837.d890dc8ca97f5de171a79408@gmail.com> (raw)
In-Reply-To: <20190116172806.GB31124@ravnborg.org>
On Wed, 16 Jan 2019 18:28:06 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:
Hi!
> On Wed, Jan 16, 2019 at 06:14:03PM +0300, Серафим Долбилов wrote:
> >
> > A new portion of questions is ready:)
> > 1. dlmalloc or tlsf - what are pros and cons of each of them?
>
> Looking at the history I could see that dlmalloc was present since barebox
> was forked from U-boot. So and old implmentation.
>
> Later tlsf was added, wihtout any explanation why.
> But based on the fact that Jean (who added tlsf) did is when we already
> had dlmalloc I tentatively conclude that tlsf is the better alternative.
> And I can see line of code is less than dlmalloc too - so maybe it is even smaller.
> I would go for tlsf based on the above and not botheting about this anymore.
Please see this Sascha's comment on tlsf:
http://lists.infradead.org/pipermail/barebox/2011-December/005288.html
At the moment we use tlsf2 in barebox. Please note that there is more recent tlsf3 at github:
https://github.com/mattconte/tlsf
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-01-16 18:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44943261547037040@iva5-750e13568e4d.qloud-c.yandex.net>
2019-01-09 12:40 ` Серафим Долбилов
2019-01-09 13:03 ` Sascha Hauer
2019-01-16 15:14 ` Серафим Долбилов
2019-01-16 15:37 ` Серафим Долбилов
2019-01-16 17:29 ` Sam Ravnborg
2019-01-16 17:28 ` Sam Ravnborg
2019-01-16 18:48 ` Antony Pavlov [this message]
2019-01-16 15:59 ` Серафим Долбилов
2019-01-17 7:59 ` Sascha Hauer
2019-01-17 12:44 ` Серафим Долбилов
2019-01-17 13:28 ` Sascha Hauer
2019-01-17 13:43 ` Roland Hieber
2019-01-17 14:48 ` Серафим Долбилов
2019-01-17 16:26 ` Sam Ravnborg
2019-01-17 21:06 ` Sascha Hauer
2019-01-18 15:01 ` Seraphim Dolbilov
2019-01-18 15:14 ` Sascha Hauer
2019-01-18 16:30 ` Seraphim Dolbilov
2019-01-21 12:34 Seraphim Dolbilov
2019-01-21 14:28 ` Seraphim Dolbilov
2019-01-21 15:12 ` Sascha Hauer
2019-01-21 15:35 ` Seraphim Dolbilov
2019-01-21 16:35 ` Sam Ravnborg
2019-01-21 16:43 ` Seraphim Dolbilov
2019-01-22 6:33 ` Sascha Hauer
2019-01-22 14:07 ` Seraphim Dolbilov
2019-01-22 14:42 ` Sascha Hauer
2019-01-22 16:12 ` Seraphim Dolbilov
2019-01-23 9:11 ` Sascha Hauer
2019-01-23 10:01 ` Seraphim Dolbilov
2019-01-23 10:17 ` Sascha Hauer
2019-01-25 12:18 ` Seraphim Dolbilov
2019-01-25 14:11 ` Seraphim Dolbilov
2019-01-28 8:46 ` Sascha Hauer
2019-01-28 8:44 ` Sascha Hauer
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=20190116214837.d890dc8ca97f5de171a79408@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.dlblv@ya.ru \
--cc=sam@ravnborg.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