From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Michal Hocko <mhocko@suse.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Dynamic Growth of Kernel Stacks
Date: Tue, 30 Apr 2024 20:20:20 -0400 [thread overview]
Message-ID: <CA+CK2bBJSa-xNpq+c1DV21XxurZzoTuVsfGF8R5w+CWzYnDRgw@mail.gmail.com> (raw)
In-Reply-To: <ZjDs-C6UUjcwM1GU@tiehlicka>
Hi Michal,
On Tue, Apr 30, 2024 at 9:07 AM Michal Hocko <mhocko@suse.com> wrote:
>
> Hi Pasha,
> is this something you still do consider interesting (and also productive
> in absence of x86 maintainers) to discuss at LSFMM?
Yes, I am going to go over a few alternatives solutions that were both
discussed in RFCv1 thread, and also a new proposal that I've been
working on.
X86 maintainers are not required, as the framework proposals are going
to be arch independent.
Pasha
next prev parent reply other threads:[~2024-05-01 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 1:03 Pasha Tatashin
2024-02-23 21:49 ` Peter Collingbourne
2024-02-23 21:56 ` Matthew Wilcox
2024-02-23 22:01 ` Peter Collingbourne
2024-04-30 13:07 ` [Lsf-pc] " Michal Hocko
2024-05-01 0:20 ` Pasha Tatashin [this message]
2024-05-02 7:19 ` Michal Hocko
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=CA+CK2bBJSa-xNpq+c1DV21XxurZzoTuVsfGF8R5w+CWzYnDRgw@mail.gmail.com \
--to=pasha.tatashin@soleen.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@suse.com \
/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