From: Yang Shi <yang.shi@linux.alibaba.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ying.huang@intel.com, tim.c.chen@intel.com, minchan@kernel.org,
daniel.m.jordan@oracle.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [v5 PATCH 1/2] mm: swap: check if swap backing device is congested or not
Date: Thu, 10 Jan 2019 16:56:29 -0800 [thread overview]
Message-ID: <bbc7bda7-62d0-df1a-23ef-d369e865bdca@linux.alibaba.com> (raw)
In-Reply-To: <20190110153147.1baf4c88bf0dd3b8a78aad08@linux-foundation.org>
On 1/10/19 3:31 PM, Andrew Morton wrote:
> On Fri, 4 Jan 2019 03:27:52 +0800 Yang Shi <yang.shi@linux.alibaba.com> wrote:
>
>> Swap readahead would read in a few pages regardless if the underlying
>> device is busy or not. It may incur long waiting time if the device is
>> congested, and it may also exacerbate the congestion.
>>
>> Use inode_read_congested() to check if the underlying device is busy or
>> not like what file page readahead does. Get inode from swap_info_struct.
>> Although we can add inode information in swap_address_space
>> (address_space->host), it may lead some unexpected side effect, i.e.
>> it may break mapping_cap_account_dirty(). Using inode from
>> swap_info_struct seems simple and good enough.
>>
>> ...
>>
>> --- a/mm/swap_state.c
>> +++ b/mm/swap_state.c
>> @@ -538,11 +538,18 @@ 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 = NULL;
>>
>> mask = swapin_nr_pages(offset) - 1;
>> if (!mask)
>> goto skip;
>>
>> + if (si->flags & (SWP_BLKDEV | SWP_FS)) {
> I re-read your discussion with Tim and I must say the reasoning behind
> this test remain foggy.
>
> What goes wrong if we just remove it?
I saw Tim already answered this.
>
> What is the status of shmem swap readahead?
shmem swap readahead will be skipped too if the underlying device is
congested.
>
> Can we at least get a comment in here which explains the reasoning?
How about like this:
diff --git a/mm/swap_state.c b/mm/swap_state.c
index 3f63bb7..85245fd 100644
--- a/mm/swap_state.c
+++ b/mm/swap_state.c
@@ -543,7 +543,8 @@ struct page *swap_cluster_readahead(swp_entry_t
entry, gfp_t gfp_mask,
if (!mask)
goto skip;
- if (si->flags & (SWP_BLKDEV | SWP_FS)) {
+ /* Test swap type to make sure the dereference is safe */
+ if (likely(si->flags & (SWP_BLKDEV | SWP_FS))) {
struct inode *inode = si->swap_file->f_mapping->host;
if (inode_read_congested(inode))
goto skip;
Tim is worried about the deference might be not safe for some corner
case, the corner cases sound unlikely by code inspection. So, added
"likely" in the if statement.
Thanks,
Yang
>
> Thanks.
>
>> + inode = si->swap_file->f_mapping->host;
>> + if (inode_read_congested(inode))
>> + goto skip;
>> + }
>> +
>> do_poll = false;
>> /* Read a page_cluster sized and aligned cluster around offset. */
prev parent reply other threads:[~2019-01-11 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 19:27 Yang Shi
2019-01-03 19:27 ` [v5 PATCH 2/2] mm: swap: add comment for swap_vma_readahead Yang Shi
2019-01-04 2:25 ` Huang, Ying
2019-01-04 2:25 ` Huang, Ying
2019-01-10 20:49 ` [v5 PATCH 1/2] mm: swap: check if swap backing device is congested or not Yang Shi
2019-01-10 23:20 ` Andrew Morton
2019-01-10 23:31 ` Andrew Morton
2019-01-10 23:40 ` Chen, Tim C
2019-01-11 0:56 ` Yang Shi [this message]
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=bbc7bda7-62d0-df1a-23ef-d369e865bdca@linux.alibaba.com \
--to=yang.shi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=tim.c.chen@intel.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