Note that there is an issue with your approach. If a migration entry is copied during fork then SWP_MIGRATION_WRITE must become SWP_MIGRATION_READ for some cases. Would you look into fixing this? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- References:
- [PATCH 0/5] Swapless page migration V2: Overview
- From: Christoph Lameter <[email protected]>
- [PATCH 5/5] Swapless V2: Revise main migration logic
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- From: KAMEZAWA Hiroyuki <[email protected]>
- [PATCH 0/5] Swapless page migration V2: Overview
- Prev by Date: [PATCH] parport_pc: fix section mismatch warnings (v2)
- Next by Date: [PATCH] modpost: relax driver data name
- Previous by thread: Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- Next by thread: Re: [PATCH 5/5] Swapless V2: Revise main migration logic
- Index(es):
 |