linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Mouna Dhaouadi <mouna.dhaouadi@umontreal.ca>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Proposal of a research paper presentation: Developers rationale analysis from the OOM-Killer of the MM module
Date: Tue, 7 Jan 2025 09:26:03 +0100	[thread overview]
Message-ID: <Z3zlG7nXgxYOKBhI@tiehlicka> (raw)
In-Reply-To: <YT3PR01MB85932360198A7445A30B0C09EC102@YT3PR01MB8593.CANPRD01.PROD.OUTLOOK.COM>

Hi,

On Mon 06-01-25 15:23:37, Mouna Dhaouadi wrote:
> Hi,
> 
> I am Mouna, a PhD Candidate at Université de Montréal.
> 
> In a previous research paper<https://dl.acm.org/doi/10.1145/3643916.3644413> (preprint available here: https://arxiv.org/pdf/2403.18832 ), we analyzed several aspects of developers rationale information from the code commit messages of the Out-Of-Memory Killer component of the Linux Kernel MM module, such as its presence, temporal evolutionn, and structure.
> 
> Would it be possible to present this work and our findings at the Linux Storage, Filesystem, Memory Management & BPF Summit<https://events.linuxfoundation.org/lsfmmbpf/> ?

Thank you for your interest in the LSFMMBPF conference. Please note that
the CfP has been announced in https://lore.kernel.org/all/Z1wQcKKw14iei0Va@tiehlicka/
This describes the process to apply for attendance as well as the format
of the conference.

Do not hesitate to get back to the organizing committee if you have any
questions.

Thanks!
-- 
Michal Hocko
SUSE Labs


  reply	other threads:[~2025-01-07  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 15:23 Mouna Dhaouadi
2025-01-07  8:26 ` Michal Hocko [this message]
2025-01-07 14:20   ` [Lsf-pc] " Mouna Dhaouadi

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=Z3zlG7nXgxYOKBhI@tiehlicka \
    --to=mhocko@suse.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mouna.dhaouadi@umontreal.ca \
    /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