From: Tim Chen <tim.c.chen@linux.intel.com>
To: Yang Shi <yang.shi@linux.alibaba.com>,
ying.huang@intel.com, tim.c.chen@intel.com, minchan@kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] mm: swap: check if swap backing device is congested or not
Date: Tue, 18 Dec 2018 11:29:25 -0800 [thread overview]
Message-ID: <6a51d47a-b87f-b0f1-4dae-843730dba698@linux.intel.com> (raw)
In-Reply-To: <1545115948-25467-1-git-send-email-yang.shi@linux.alibaba.com>
On 12/17/18 10:52 PM, Yang Shi wrote:
>
> diff --git a/mm/swap_state.c b/mm/swap_state.c
> index fd2f21e..7cc3c29 100644
> --- a/mm/swap_state.c
> +++ b/mm/swap_state.c
> @@ -538,11 +538,15 @@ struct page *swap_cluster_readahead(swp_entry_t entry, gfp_t gfp_mask,
> bool do_poll = true, page_allocated;
> struct vm_area_struct *vma = vmf->vma;
> unsigned long addr = vmf->address;
> + struct inode *inode = si->swap_file->f_mapping->host;
>
> mask = swapin_nr_pages(offset) - 1;
> if (!mask)
> goto skip;
>
Shmem will also be using this function and I don't think the inode_read_congested
logic is relevant for that case.
So probably change the check to
if (swp_type(entry) < nr_swapfiles &&
inode_read_congested(si->swap_file->f_mapping->host))
goto skip;
> + if (inode_read_congested(inode))
> + goto skip;
> +
> do_poll = false;
> /* Read a page_cluster sized and aligned cluster around offset. */
> start_offset = offset & ~mask;
>
Thanks.
Tim
next prev parent reply other threads:[~2018-12-18 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 6:52 Yang Shi
2018-12-18 6:52 ` [RFC PATCH 2/2] mm: swap: add comment for swap_vma_readahead Yang Shi
2018-12-18 19:29 ` Tim Chen [this message]
2018-12-18 23:43 ` [RFC PATCH 1/2] mm: swap: check if swap backing device is congested or not Yang Shi
2018-12-19 0:16 ` Tim Chen
2018-12-19 5:56 ` Yang Shi
2018-12-19 17:28 ` Tim Chen
2018-12-19 18:40 ` Yang Shi
2018-12-19 19:00 ` Tim Chen
2018-12-19 23:48 ` Yang Shi
2018-12-20 1:05 ` Tim Chen
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=6a51d47a-b87f-b0f1-4dae-843730dba698@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=tim.c.chen@intel.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.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