From: Florian Weimer <fweimer@redhat.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Cc: libc-alpha@sourceware.org, adhemerval.zanella@linaro.org,
munroesj@linux.vnet.ibm.com
Subject: Re: [PATCH v3] PowerPC: libc single-thread lock optimization
Date: Fri, 11 Mar 2016 18:39:00 -0000 [thread overview]
Message-ID: <56E310BF.303@redhat.com> (raw)
In-Reply-To: <1457721337-30897-1-git-send-email-tuliom@linux.vnet.ibm.com>
On 03/11/2016 07:35 PM, Tulio Magno Quites Machado Filho wrote:
> diff --git a/malloc/malloc.c b/malloc/malloc.c
> index b8a43bf..1eed794 100644
> --- a/malloc/malloc.c
> +++ b/malloc/malloc.c
> @@ -4150,7 +4150,7 @@ static void malloc_consolidate(mstate av)
> maxfb = &fastbin (av, NFASTBINS - 1);
> fb = &fastbin (av, 0);
> do {
> - p = atomic_exchange_acq (fb, 0);
> + p = atomic_exchange_acq (fb, NULL);
> if (p != 0) {
> do {
> check_inuse_chunk(av, p);
This should go in immediately and separately, it is independent of the
rest of the patch.
Thanks,
Florian
next prev parent reply other threads:[~2016-03-11 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 13:50 [PATCH v2] " Adhemerval Zanella
2014-08-22 14:00 ` Future atomic operation cleanup Richard Henderson
2014-08-22 14:50 ` Joseph S. Myers
2014-08-22 17:26 ` Torvald Riegel
2014-08-28 13:57 ` Adhemerval Zanella
2014-08-28 15:37 ` Torvald Riegel
2014-08-28 16:28 ` Adhemerval Zanella
2014-08-29 9:55 ` Torvald Riegel
2014-08-29 11:10 ` Adhemerval Zanella
2014-08-29 13:28 ` Torvald Riegel
2014-08-29 13:32 ` Adhemerval Zanella
2014-08-29 16:33 ` Chris Metcalf
2014-10-23 17:12 ` Carlos O'Donell
2014-08-29 21:52 ` Roland McGrath
2014-09-05 17:51 ` Torvald Riegel
2016-03-11 18:36 ` [PATCH v3] PowerPC: libc single-thread lock optimization Tulio Magno Quites Machado Filho
2016-03-11 18:39 ` Florian Weimer [this message]
2016-03-11 21:12 ` Tulio Magno Quites Machado Filho
2016-03-28 17:36 ` [PING][PATCH " Tulio Magno Quites Machado Filho
2016-04-07 11:24 ` [PATCH " Torvald Riegel
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=56E310BF.303@redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=munroesj@linux.vnet.ibm.com \
--cc=tuliom@linux.vnet.ibm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).