SPARSEMEM: pfn_to_nid implementation
Get series with b4
b4 am exportbomb.1132181992@pinkyVersions newest first
- v1 Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | kvaddr_to_nid not used in common codeinclude/ include/ | +0 | 0 replies | |
| 2/3 | pfn_to_pgdat not used in common codeinclude/ | +0 | 0 replies | |
| 3/3 | sparse provide pfn_to_nidinclude/ | +5 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] SPARSEMEM: pfn_to_nid implementation
I have reviewed the uses of pfn_to_nid() in 2.6.14-mm2. The only user of the non-init pfn_to_nid is the one in check_pte_range(). So we simply need to profide a non-early pfn_to_nid() implementation for SPARSEMEM. Whilst reviewing these interfaces I found two alternative dependant interfaces which are not used.
Following this message are three patches:
kvaddr_to_nid-not-used-in-common-code: removes the unused interface kvaddr_to_nid().
pfn_to_pgdat-not-used-in-common-code: removes the unused interface pfn_to_pgdat().
sparse-provide-pfn_to_nid: provides pfn_to_nid() for SPARSEMEM. Note that this implmentation assumes the pfn has been validated prior to use. The only intree user of this call does this. We perhaps need to make this part of the signature for this function.
Mike, how does this look to you?
-apw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>