public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: xry111@xry111.site, libc-alpha@sourceware.org
Subject: Re: posix_memalign performance regression in 2.38?
Date: Mon, 07 Aug 2023 15:49:46 -0400	[thread overview]
Message-ID: <xn350ur5t1.fsf@greed.delorie.com> (raw)
In-Reply-To: <067bed0b-87f6-abbb-0e2a-14ee1a0ac0f9@linaro.org> (message from Adhemerval Zanella Netto on Fri, 4 Aug 2023 11:12:44 -0300)

Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:
> It seems to be caused by 24cdd6c71debfd10a9f7cb217fe2a2c4c486ed6f, where
> posix_memalign now calls chunk_ok_for_memalign (which takes most of time).
>
> DJ, any idea on how we can improve this?

This was not unexpected, as we're adding more logic to the memalign
family of functions in order to use less memory.  We can do some
optimizations in this area but it will remain a balancing act between
speed and memory usage.

The old code was terrible wrt memory usage.


  reply	other threads:[~2023-08-07 19:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  2:52 Xi Ruoyao
2023-08-04 14:12 ` Adhemerval Zanella Netto
2023-08-07 19:49   ` DJ Delorie [this message]
2023-08-07 19:57     ` Sam James
2023-08-07 20:15       ` DJ Delorie
2023-08-08  3:38       ` DJ Delorie
2023-08-08  8:08         ` Xi Ruoyao
2023-08-08 15:08           ` DJ Delorie
2023-08-09 10:47           ` Florian Weimer
2023-08-09 16:59             ` Florian Weimer
2023-08-07 19:58     ` Noah Goldstein
2023-08-07 20:07       ` DJ Delorie

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=xn350ur5t1.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=xry111@xry111.site \
    /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).