From: Aryan Kaushik <aryankaushik666@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: LSF/MM + BPF ATTEND - Topic 2 for discussion
Date: Tue, 4 Feb 2025 02:05:22 +0000 [thread overview]
Message-ID: <CAHnJ_vjuYy9gHz8Tb0AJUYhnYSfKZBMW4ShMXguVy8qCiW_eFw@mail.gmail.com> (raw)
Hi Team
Hope this email finds you well.
Topic: Memory Management Optimization for High-Performance Computing
Description: HPC applications demand highly efficient memory
management for optimal performance.
This session would examine NUMA optimizations, memory allocation
strategies, and cache management to improve memory performance in
compute-heavy workloads.
We could also discuss the impact of memory fragmentation and ways to
reduce latency in HPC environments.
My Contribution: I have been exploring memory management techniques,
especially in performance-critical applications.
I’d like to discuss potential inefficiencies and suggest improvements
tailored for modern HPC workloads.
Please feel free to share your insight on the topic.
Best Regards
Aryan Kaushik
reply other threads:[~2025-02-04 2:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHnJ_vjuYy9gHz8Tb0AJUYhnYSfKZBMW4ShMXguVy8qCiW_eFw@mail.gmail.com \
--to=aryankaushik666@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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