[Question] Why PageReadahead is not migrated by migration code?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>
- Subject: [Question] Why PageReadahead is not migrated by migration code?
- From: Yang Shi <yang.shi@xxxxxxxxxxxxxxxxx>
- Date: Thu, 13 Feb 2020 09:06:58 -0800
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
Hi folks,
Recently we saw some PageReadahead related bugs, so I did a quick check
about the use of PageReadahead. I just found the state is *not* migrated
by migrate_page_states().
Since migrate_page() won't migrate writeback page, so if PageReadahead
is set it should just mean PG_readahead rather than PG_reclaim. So, I
didn't think of why it is not migrated.
I dig into the history a little bit, but the change in migration code is
too overwhelming. But, it looks PG_readahead was added after migration
was introduced. Is it just a simple omission?
Thanks,
Yang
[Index of Archives]
[Linux ARM Kernel]
[Linux ARM]
[Linux Omap]
[Fedora ARM]
[IETF Annouce]
[Bugtraq]
[Linux OMAP]
[Linux MIPS]
[eCos]
[Asterisk Internet PBX]
[Linux API]