From: Charles Forsyth <charles.forsyth@gmail.com>
To: Oleg <lego12239@yandex.ru>,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] atexit() & atexitdont()
Date: Fri, 7 Nov 2014 10:22:26 +0000 [thread overview]
Message-ID: <CAOw7k5hYE9b5U8y8WfFKPbOP+U1550qTB+0HNJseFHnP0yHfQQ@mail.gmail.com> (raw)
In-Reply-To: <20141107094425.GA29497@localhost>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On 7 November 2014 09:44, Oleg <lego12239@yandex.ru> wrote:
> f malloc works like in linux (at first invocation allocate more bytes than
> requested and then each malloc() use this already allocated by kernel area
> of memory), i think this isn't a big performance impact.
>
I wasn't really thinking about performance; as I said it's unlikely to be
in a critical path.
This is according to manual. Because now if we use atexit() with
> atexitdont()
> we see the wrong behaviour from manual point of view.
Yes, that's why I suggested fixing atexitdont to move any remaining values
down the array.
[-- Attachment #2: Type: text/html, Size: 1450 bytes --]
next prev parent reply other threads:[~2014-11-07 10:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 21:05 Oleg
2014-11-06 21:26 ` erik quanstrom
2014-11-06 21:42 ` Skip Tavakkolian
2014-11-06 21:44 ` Skip Tavakkolian
2014-11-06 22:50 ` lego12239
2014-11-06 22:45 ` Oleg
2014-11-07 7:17 ` k0ga
2014-11-07 8:02 ` Oleg
2014-11-07 8:19 ` Charles Forsyth
2014-11-07 9:44 ` Oleg
2014-11-07 10:22 ` Charles Forsyth [this message]
2014-11-07 11:05 ` Oleg
2014-11-07 10:57 ` Steffen Nurpmeso
2014-11-07 11:49 ` Charles Forsyth
2014-11-07 12:19 ` Oleg
2014-11-07 12:27 ` Charles Forsyth
2014-11-07 19:53 ` erik quanstrom
2014-11-07 20:30 ` Oleg
2014-11-07 19:25 ` Steffen Nurpmeso
2014-11-07 17:45 sl
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=CAOw7k5hYE9b5U8y8WfFKPbOP+U1550qTB+0HNJseFHnP0yHfQQ@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
--cc=lego12239@yandex.ru \
/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;
as well as URLs for NNTP newsgroup(s).