From: Mel Gorman <mgorman@techsingularity.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "??????(Caspar)" <jinli.zjl@alibaba-inc.com>,
green@linuxhacker.ru, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"??????(??????)" <zhiche.yy@alibaba-inc.com>,
?????? <shidao.ytt@alibaba-inc.com>
Subject: Re: [PATCH] mm/fadvise: discard partial pages iff endbyte is also eof
Date: Thu, 4 Jan 2018 10:05:53 +0000 [thread overview]
Message-ID: <20180104094513.46dhslsphmh2a462@techsingularity.net> (raw)
In-Reply-To: <20180103161753.8b22d32d640f6e0be4119081@linux-foundation.org>
On Wed, Jan 03, 2018 at 04:17:53PM -0800, Andrew Morton wrote:
> : invalidate_mapping_pages() takes start/end, but fadvise is currently passing
> : it start/len.
> :
> :
> :
> : mm/fadvise.c | 8 ++++++--
> : 1 files changed, 6 insertions(+), 2 deletions(-)
> :
> : diff -puN mm/fadvise.c~fadvise-fix mm/fadvise.c
> : --- 25/mm/fadvise.c~fadvise-fix 2003-08-14 18:16:12.000000000 -0700
> : +++ 25-akpm/mm/fadvise.c 2003-08-14 18:16:12.000000000 -0700
> : @@ -26,6 +26,8 @@ long sys_fadvise64(int fd, loff_t offset
> : struct inode *inode;
> : struct address_space *mapping;
> : struct backing_dev_info *bdi;
> : + pgoff_t start_index;
> : + pgoff_t end_index;
> : int ret = 0;
> :
> : if (!file)
> : @@ -65,8 +67,10 @@ long sys_fadvise64(int fd, loff_t offset
> : case POSIX_FADV_DONTNEED:
> : if (!bdi_write_congested(mapping->backing_dev_info))
> : filemap_flush(mapping);
> : - invalidate_mapping_pages(mapping, offset >> PAGE_CACHE_SHIFT,
> : - (len >> PAGE_CACHE_SHIFT) + 1);
> : + start_index = offset >> PAGE_CACHE_SHIFT;
> : + end_index = (offset + len + PAGE_CACHE_SIZE - 1) >>
> : + PAGE_CACHE_SHIFT;
> : + invalidate_mapping_pages(mapping, start_index, end_index);
> : break;
> : default:
> : ret = -EINVAL;
> :
>
> So I'm not sure that the whole "don't discard partial pages" thing is
> well-founded and I see no reason why we cannot alter it.
>
> So, thinking caps on: why not just discard them? After all, that's
> what userspace asked us to do.
>
We could, it just means that any application that accidentally discards
hot data due to an unaligned fadvise will incur more IO. We've no idea
how many, if any applications, do this.
--
Mel Gorman
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-04 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 4:16 十刀
2018-01-03 6:53 ` 夷则(Caspar)
2018-01-03 10:48 ` Mel Gorman
2018-01-04 0:17 ` Andrew Morton
2018-01-04 8:17 ` 夷则(Caspar)
2018-01-04 22:54 ` Andrew Morton
2018-01-04 10:05 ` Mel Gorman [this message]
2018-01-04 6:13 ` 夷则(Caspar)
2018-01-04 7:44 ` 夷则(Caspar)
2018-01-04 11:34 ` Mel Gorman
2018-01-04 11:38 ` 夷则(Caspar)
2018-01-05 6:10 ` [PATCH v2] mm/fadvise: discard partial page if endbyte is also EOF 夷则(Caspar)
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=20180104094513.46dhslsphmh2a462@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=green@linuxhacker.ru \
--cc=jinli.zjl@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shidao.ytt@alibaba-inc.com \
--cc=zhiche.yy@alibaba-inc.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