From: Charan Teja Kalla <quic_charante@quicinc.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: <akpm@linux-foundation.org>, <hughd@google.com>,
<willy@infradead.org>, <markhemm@googlemail.com>,
<rientjes@google.com>, <shakeelb@google.com>, <mhocko@suse.com>,
<vbabka@suse.cz>, <quic_pkondeti@quicinc.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V6 2/2] mm: shmem: implement POSIX_FADV_[WILL|DONT]NEED for shmem
Date: Wed, 8 Feb 2023 20:24:54 +0530 [thread overview]
Message-ID: <8f40873d-8a9c-bcec-6742-885478365e4c@quicinc.com> (raw)
In-Reply-To: <CAJuCfpH7Jag9qEcKjGTx9Qv_oekM6qRVkGwzTrXShgYbLdLKtg@mail.gmail.com>
Thanks Suren!!
On 2/8/2023 4:18 AM, Suren Baghdasaryan wrote:
>> +static int shmem_fadvise(struct file *file, loff_t offset, loff_t len, int advice)
>> +{
>> + loff_t endbyte;
>> + pgoff_t start_index;
>> + pgoff_t end_index;
>> + struct address_space *mapping;
>> + struct inode *inode = file_inode(file);
>> + int ret = 0;
>> +
>> + if (S_ISFIFO(inode->i_mode))
>> + return -ESPIPE;
>> +
>> + mapping = file->f_mapping;
>> + if (!mapping || len < 0 || !shmem_mapping(mapping))
>> + return -EINVAL;
>> +
>> + endbyte = fadvise_calc_endbyte(offset, len);
>> +
>> + start_index = offset >> PAGE_SHIFT;
>> + end_index = endbyte >> PAGE_SHIFT;
>> + switch (advice) {
>> + case POSIX_FADV_DONTNEED:
> Should (SHMEM_I(inode)->flags & VM_LOCKED) be checked here too?
>
Is this w.r.t context from shmem_lock() perspective which does set this
flag? If so, Isn't the PageUnevictable check cover this part? And to
avoid unnecessary Unevictable check later on the locked shmem file, How
about just checking mapping_unevictable() before performing
shmem_fadvise_dontneed)()? Please let me know If I failed to get your point.
>> + ret = shmem_fadvise_dontneed(mapping, start_index, end_index);
>> + break;
>> + case POSIX_FADV_WILLNEED:
>> + ret = shmem_fadvise_willneed(mapping, start_index, end_index);
>> + break;
>> + case POSIX_FADV_NORMAL:
>> + case POSIX_FADV_RANDOM:
>> + case POSIX_FADV_SEQUENTIAL:
>> + case POSIX_FADV_NOREUSE:
--Charan
next prev parent reply other threads:[~2023-02-08 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:21 [PATCH V6 0/2] mm: shmem: support POSIX_FADV_[WILL|DONT]NEED for shmem files Charan Teja Kalla
2023-02-06 14:21 ` [PATCH V6 1/2] mm: fadvise: move 'endbyte' calculations to helper function Charan Teja Kalla
2023-02-06 14:21 ` [PATCH V6 2/2] mm: shmem: implement POSIX_FADV_[WILL|DONT]NEED for shmem Charan Teja Kalla
2023-02-06 16:18 ` Matthew Wilcox
2023-02-07 4:46 ` Charan Teja Kalla
2023-02-07 22:48 ` Suren Baghdasaryan
2023-02-08 14:54 ` Charan Teja Kalla [this message]
2023-02-08 22:51 ` Suren Baghdasaryan
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=8f40873d-8a9c-bcec-6742-885478365e4c@quicinc.com \
--to=quic_charante@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=markhemm@googlemail.com \
--cc=mhocko@suse.com \
--cc=quic_pkondeti@quicinc.com \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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