Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1351234 > unrolled thread
| Started by | Balbir Singh <bsingharora@gmail.com> |
|---|---|
| First post | 2016-03-07 02:00 +0100 |
| Last post | 2016-03-07 07:40 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v1 02/11] mm: thp: introduce CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION Balbir Singh <bsingharora@gmail.com> - 2016-03-07 02:00 +0100
Re: [PATCH v1 02/11] mm: thp: introduce CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> - 2016-03-07 07:40 +0100
| From | Balbir Singh <bsingharora@gmail.com> |
|---|---|
| Date | 2016-03-07 02:00 +0100 |
| Subject | Re: [PATCH v1 02/11] mm: thp: introduce CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION |
| Message-ID | <r9RGF-41Z-5@gated-at.bofh.it> |
On Thu, Mar 03, 2016 at 04:41:49PM +0900, Naoya Horiguchi wrote: > Introduces CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION to limit thp migration > functionality to x86_64, which should be safer at the first step. > The changelog is not helpful. Could you please describe what is architecture specific in these changes? What do other arches need to do to port these changes over?
[toc] | [next] | [standalone]
| From | Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> |
|---|---|
| Date | 2016-03-07 07:40 +0100 |
| Message-ID | <r9WZI-7HZ-9@gated-at.bofh.it> |
| In reply to | #1351234 |
On Mon, Mar 07, 2016 at 11:58:04AM +1100, Balbir Singh wrote: > On Thu, Mar 03, 2016 at 04:41:49PM +0900, Naoya Horiguchi wrote: > > Introduces CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION to limit thp migration > > functionality to x86_64, which should be safer at the first step. > > > > The changelog is not helpful. Could you please describe what is > architecture specific in these changes? What do other arches need to do > to port these changes over? The arch specific parts are pmd_present() and swap entry format. Currently pmd_present() in x86_64 is not simple enough to easily determine pmd's state (none, normal pmd entry pointing to pte page, pmd for thp, or pmd migration entry ...) That requires me to assume in this version that pmd migration entry should have_PAGE_PSE set, which should not be necessary if the complexity is fixed. So I will mention this pmd_present() problem in the next version. So if it's fixed, what developers need to do to port this feature to their architectures is just to enable CONFIG_ARCH_ENABLE_THP_MIGRATION (and test it.) Thanks, Naoya Horiguchi
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web