public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Arjan van de Ven via Libc-alpha <libc-alpha@sourceware.org>
Cc: Sunil Pandey <skpgkp2@gmail.com>,
	 Andreas Schwab <schwab@linux-m68k.org>,
	 Libc-stable Mailing List <libc-stable@sourceware.org>,
	 Arjan van de Ven <arjan@linux.intel.com>,
	"Paul A . Clarke" <pc@us.ibm.com>
Subject: Re: [PATCH v6 4/4] Avoid extra load with CAS in __pthread_mutex_clocklock_common [BZ #28537]
Date: Sun, 11 Sep 2022 23:26:29 +0200	[thread overview]
Message-ID: <87czc11u2i.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <5ba017f8-b7d3-12a0-4186-d57ff48eac26@linux.intel.com> (Arjan van de Ven via Libc-alpha's message of "Sun, 11 Sep 2022 13:15:15 -0700")

* Arjan van de Ven via Libc-alpha:

> what exactly is the stable branch policy that would suggest to
> backport performance improvements like this ?  (most projects are
> sticking to "strict bugfixes and other gross oversights" as much as
> possible)

We occasionally backport safe (and not-so-safe) performance
optimizations.  We draw the line at ABI changes, those aren't possible.
It's also very desirable that all future releases have a superset of the
backports.

But anything else depends on who is willing to do the work.

Thanks,
Florian


  reply	other threads:[~2022-09-11 21:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211111162428.2286605-1-hjl.tools@gmail.com>
     [not found] ` <20211111162428.2286605-5-hjl.tools@gmail.com>
     [not found]   ` <87v90xryvi.fsf@igel.home>
2022-09-11 20:12     ` Sunil Pandey
2022-09-11 20:15       ` Arjan van de Ven
2022-09-11 21:26         ` Florian Weimer [this message]
2022-09-29  0:09       ` Noah Goldstein
     [not found] ` <20211111162428.2286605-3-hjl.tools@gmail.com>
     [not found]   ` <87zgq9rywl.fsf@igel.home>
2022-09-11 20:16     ` [PATCH v6 2/4] Avoid extra load with CAS in __pthread_mutex_lock_full " Sunil Pandey
2022-09-29  0:10       ` Noah Goldstein
     [not found] ` <20211111162428.2286605-2-hjl.tools@gmail.com>
     [not found]   ` <CAFUsyfJH45MshHkFjohENvhJzt1bC=PrUH_3xRn1KubGy9X1HA@mail.gmail.com>
     [not found]     ` <CAMe9rOqOv3WC9rWwtFyzc7rJFDDbNTAfTio-FZC4oW5y751FWA@mail.gmail.com>
     [not found]       ` <CAFUsyf+Yf=QM-0Zj31=k6fANCdXa6XnzVn=Kj6im3xDYbanbnA@mail.gmail.com>
     [not found]         ` <CAMe9rOpE1+1zqtA4xqJNy-RK03jXNzv-JnYSJFtGmtqSa2QqQQ@mail.gmail.com>
     [not found]           ` <924a80cd-202c-99e9-a2d9-1aeda2235b83@linux.intel.com>
2022-09-11 20:19             ` [PATCH v6 1/4] Add LLL_MUTEX_READ_LOCK " Sunil Pandey
2022-09-29  0:10               ` Noah Goldstein

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=87czc11u2i.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=arjan@linux.intel.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-stable@sourceware.org \
    --cc=pc@us.ibm.com \
    --cc=schwab@linux-m68k.org \
    --cc=skpgkp2@gmail.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).