From: DJ Delorie <dj@redhat.com>
To: Sam James <sam@gentoo.org>
Cc: adhemerval.zanella@linaro.org, xry111@xry111.site,
libc-alpha@sourceware.org, dilfridge@gentoo.org,
timo@rothenpieler.org
Subject: Re: posix_memalign performance regression in 2.38?
Date: Mon, 07 Aug 2023 16:15:31 -0400 [thread overview]
Message-ID: <xntttapq1o.fsf@greed.delorie.com> (raw)
In-Reply-To: <878ramtybs.fsf@gentoo.org> (message from Sam James on Mon, 07 Aug 2023 20:57:26 +0100)
Sam James <sam@gentoo.org> writes:
> We've had a bunch of reports of this impacting mpv and ffmpeg as well,
> so it's not contrived FWIW.
Hmm... that sounds like a bug, not a performance issue. I'll try to
reproduce it locally.
next prev parent reply other threads:[~2023-08-07 20:15 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
2023-08-07 19:57 ` Sam James
2023-08-07 20:15 ` DJ Delorie [this message]
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=xntttapq1o.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.org \
--cc=sam@gentoo.org \
--cc=timo@rothenpieler.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).