From: chaithco@redhat.com
To: Usama Arif <usama.arif@linux.dev>
Cc: muchun.song@linux.dev, osalvador@suse.de,
akpm@linux-foundation.org, david@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, arozansk@redhat.com
Subject: Re: [PATCH v2] Respect mempolicy when calculating surplus huge pages.
Date: Fri, 03 Jul 2026 10:46:53 -0600 [thread overview]
Message-ID: <5MYLHT.GMWUJM8EWIEO3@redhat.com> (raw)
In-Reply-To: <20260624144600.8159-1-usama.arif@linux.dev>
On Wed, Jun 24 2026 at 07:45:59 AM -07:00:00, Usama Arif
<usama.arif@linux.dev> wrote:
> > +static void setup_threads(void) {
> > + per_thread_args = calloc(2, sizeof(per_thread_args));
>
> Should we do calloc(2, sizeof(*per_thread_args)) here?
Yes! My apologies; my intent is to allocate two thread_args here not
allocate pointers. I can fix that up.
prev parent reply other threads:[~2026-07-03 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 18:45 [PATCH v2] Respect mempolicy when calculating surplus huge pages Charles Haithcock
2026-06-23 19:44 ` Joshua Hahn
2026-06-24 14:45 ` Usama Arif
2026-07-03 16:46 ` chaithco [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=5MYLHT.GMWUJM8EWIEO3@redhat.com \
--to=chaithco@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arozansk@redhat.com \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=usama.arif@linux.dev \
/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