public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Norbert Manthey <nmanthey@conp-solutions.com>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [[RFC][PATCH] v1 0/2] malloc/realloc with transparent huge page support
Date: Mon, 4 May 2020 23:44:45 +0200	[thread overview]
Message-ID: <b4463978-a833-6a49-aedf-99f0b2baaed3@conp-solutions.com> (raw)
In-Reply-To: <xnmu6n76kg.fsf@greed.delorie.com>

On 04.05.20 23:07, DJ Delorie wrote:

> Norbert Manthey <nmanthey@conp-solutions.com> writes:
>> I have been looking for a way to enable huge pages in a user land process
>> without privileges, and without modifying the source of the process.
> In addition to the other feedback you've gotten, I'll point out some
> administrivia...
>
> * Non-trivial patches require a copyright assignment before we can act
>   on them (really, before we should even look at them).  The process is
>   easy and we can help you though it, but it does take time.
I understand, and am willing to move forward with this. I reached out to
assign@gnu.org.
>
> * Patches should be against current master and use the latest
>   conventions (like tunables) - at least, by the time you want them
>   included.  2.23 is "ancient" for us and a lot has changed in the
>   malloc code since then.  Your findings from that version may not be
>   the same as findings against master.

I understand. I will follow the provided feedback (migrate to tunables;
use a macro for the huge page size to be used), and can test whether the
speedup obtained for version 2.23 is comparable to what we would get
when starting from the current HEAD commit

Best,
Norbert



  reply	other threads:[~2020-05-04 21:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03 22:07 Norbert Manthey
2020-05-03 22:07 ` [[RFC][PATCH] v1 1/2] malloc: support transparent huge pages Norbert Manthey
2020-05-03 22:07 ` [[RFC][PATCH] v1 2/2] malloc: improve THP effectiveness Norbert Manthey
2020-05-03 22:21   ` Andrew Pinski
2020-05-03 22:15 ` [[RFC][PATCH] v1 0/2] malloc/realloc with transparent huge page support H.J. Lu
2020-05-04  4:36 ` Florian Weimer
2020-05-04  6:58   ` Norbert Manthey
2020-05-04  7:07     ` Florian Weimer
2020-05-04 21:07 ` DJ Delorie
2020-05-04 21:44   ` Norbert Manthey [this message]
     [not found] <7bd30e6c-7ae8-4c03-a818-6309351b3df9@email.android.com>
2020-05-04  8:27 ` Florian Weimer
2020-05-04 13:31   ` Adhemerval Zanella

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=b4463978-a833-6a49-aedf-99f0b2baaed3@conp-solutions.com \
    --to=nmanthey@conp-solutions.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.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).