From: Andrew Morton <akpm@linux-foundation.org>
To: Charan Teja Kalla <quic_charante@quicinc.com>
Cc: <willy@infradead.org>, <markhemm@googlemail.com>,
<hughd@google.com>, <rientjes@google.com>, <surenb@google.com>,
<shakeelb@google.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND V5,2/2] mm: shmem: implement POSIX_FADV_[WILL|DONT]NEED for shmem
Date: Tue, 7 Jun 2022 11:24:17 -0700 [thread overview]
Message-ID: <20220607112417.5b47a5f55f20fe1f6cfb14e6@linux-foundation.org> (raw)
In-Reply-To: <7584364f-3aaf-282a-0a67-d8329a3415dc@quicinc.com>
On Tue, 7 Jun 2022 20:22:34 +0530 Charan Teja Kalla <quic_charante@quicinc.com> wrote:
> > Is there an actual userspace/driver combination which will use this?
> > Has the new feature been tested in such an arrangement? And if so,
> > which driver(s)?
> >
>
> Currently my organization is using this setup where it does makes use of
> the shmem infrastructure to allocate the pages and its fd is passed to
> the user. The user is now deciding on when to reclaim these pages to
> free up the memory through already presented vfs_fadvise(DONTNEED)
> system call and bringing back them through vfs_fadvise(WILLNEED), when
OK, thanks. Please capture all these thoughts in the [0/n] changelog,
leave it a few days for reviewer input then resend and I'll take a
closer look.
The patches don't seem to be getting a lot of traction.
next prev parent reply other threads:[~2022-06-07 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 6:38 [PATCH RESEND V5,0/2]mm: shmem: support POSIX_FADV_[WILL|DONT]NEED for shmem files Charan Teja Kalla
2022-03-31 6:38 ` [PATCH RESEND V5,1/2] mm: fadvise: move 'endbyte' calculations to helper function Charan Teja Kalla
2022-03-31 6:38 ` [PATCH RESEND V5,2/2] mm: shmem: implement POSIX_FADV_[WILL|DONT]NEED for shmem Charan Teja Kalla
2022-05-31 21:21 ` Andrew Morton
2022-06-07 14:52 ` Charan Teja Kalla
2022-06-07 18:24 ` Andrew Morton [this message]
2023-01-24 16:01 ` Matthew Wilcox
2023-01-24 13:28 ` [PATCH RESEND V5,0/2]mm: shmem: support POSIX_FADV_[WILL|DONT]NEED for shmem files Charan Teja Kalla
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=20220607112417.5b47a5f55f20fe1f6cfb14e6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=markhemm@googlemail.com \
--cc=quic_charante@quicinc.com \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=surenb@google.com \
--cc=willy@infradead.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