unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Chung-Lin Tang <chunglin_tang@mentor.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
	GLIBC Devel <libc-alpha@sourceware.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	<cltang@codesourcery.com>, Carlos O'Donell <carlos@redhat.com>,
	<arjun@redhat.com>
Subject: Re: 2.31: glibc master is now kinda, sorta, frozen
Date: Mon, 6 Jan 2020 23:41:44 +0800	[thread overview]
Message-ID: <8ec518f7-50a1-3120-7af8-26281a57fe74@mentor.com> (raw)
In-Reply-To: <c590370f-f0b0-e653-1cc1-89183a802011@gotplt.org>

On 2020/1/1 12:29 AM, Siddhesh Poyarekar wrote:
> - New DSO sorting algorithm and test script
>      https://sourceware.org/ml/libc-alpha/2019-07/msg00472.html
>      https://sourceware.org/ml/libc-alpha/2019-07/msg00473.html
> 
> Chung-Lin, based on Carlos' review comments, a new revision looks like a
> fair amount of work, which makes this unsuitable as a release blocker.
> I suggest we drop this from the blocker list so that you're not rushed
> into pushing a patchset.  Please do post the patch for review in the
> meantime since we're still OK to do reviews; just that you can only
> commit after the 2.31 release is done.

Hi Siddhesh,
as Carlos' review suggests, and what I'm working on right now, can this still
make 2.31 as a non-default tunable option? Since the new algorithm does have
some slight behavior difference, it may be better to make available earlier
than later for users to try.

I will try to update the patches and respond to Carlos' review in detail within
the week.

Thanks,
Chung-Lin

  parent reply	other threads:[~2020-01-06 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 16:29 2.31: glibc master is now kinda, sorta, frozen Siddhesh Poyarekar
2019-12-31 16:53 ` Adhemerval Zanella
2019-12-31 16:59   ` Adhemerval Zanella
2019-12-31 17:05 ` Rafal Luzynski
2020-01-06 15:41 ` Chung-Lin Tang [this message]
2020-01-06 15:46   ` Siddhesh Poyarekar
2020-01-07  9:07     ` Chung-Lin Tang
2020-01-07 22:15       ` Carlos O'Donell
2020-01-06 16:18 ` Arjun Shankar
2020-01-06 16:22   ` Siddhesh Poyarekar
2020-01-06 18:08     ` Arjun Shankar

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ec518f7-50a1-3120-7af8-26281a57fe74@mentor.com \
    --to=chunglin_tang@mentor.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=arjun@redhat.com \
    --cc=carlos@redhat.com \
    --cc=cltang@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.org \
    /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).