public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Support dl-tunables.list in subdirectories
Date: Thu, 25 May 2017 12:35:00 -0000	[thread overview]
Message-ID: <CAMe9rOpFZAEJoVyBnwnARop7SHyLeeWmiqwKrgbzcZLMsOmqoQ@mail.gmail.com> (raw)
In-Reply-To: <11468384-3c04-03a7-d6b4-7fb7e83f1714@gotplt.org>

On Wed, May 24, 2017 at 11:06 PM, Siddhesh Poyarekar
<siddhesh@gotplt.org> wrote:
> On Thursday 25 May 2017 01:11 AM, H.J. Lu wrote:
>> We can put processor specific tunables in dl-tunables.list under
>> sysdeps instead of in elf/dl-tunables.list.
>>
>> Any comments?
>
> That makes sense.  However, please avoid putting processor/arch

I will check in my patch.

> information in the tunable names.  That is, instead of glibc.x86_tune or
> something like that, stick to glibc.tune[1].  That way if the tunable is
> deemed to be applicable to other architectures in future, then we can
> simply move it to the generic list.

Sure, we can discuss when I submit my patch.

Thanks.

> Siddhesh
>
> [1] Any processor/hardware feature tuning should go into the glibc.tune
> namespace. I see you're looking to implement IFUNC overrides, so the
> tunable I've proposed for that is glibc.tune.mcpu where the values
> should map to those in gcc.



-- 
H.J.

      reply	other threads:[~2017-05-25 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 19:41 H.J. Lu
2017-05-25  6:08 ` Siddhesh Poyarekar
2017-05-25 12:35   ` H.J. Lu [this message]

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=CAMe9rOpFZAEJoVyBnwnARop7SHyLeeWmiqwKrgbzcZLMsOmqoQ@mail.gmail.com \
    --to=hjl.tools@gmail.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).