diff for duplicates of <87a8ge492u.fsf@linux.vnet.ibm.com> diff --git a/a/1.txt b/N1/1.txt index f3d66e0..bdb747a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,6 +1,6 @@ christophe leroy <christophe.leroy@c-s.fr> writes: -> Le 14/08/2016 =C3=A0 16:27, Aneesh Kumar K.V a =C3=A9crit : +> Le 14/08/2016 à 16:27, Aneesh Kumar K.V a écrit : >> Christophe Leroy <christophe.leroy@c-s.fr> writes: >> >>> This set provides implementation of huge pages on the 8xx @@ -17,20 +17,18 @@ christophe leroy <christophe.leroy@c-s.fr> writes: >> May be that can be sent as a separate series ? >> > -> Patch 2 is a lack in gup_hugepte: on 8xx, _PAGE_RW (hence _PAGE_WRITE)=20 -> is defined as 0 and _PAGE_RO must be set when the page in not writeable.= -=20 +> Patch 2 is a lack in gup_hugepte: on 8xx, _PAGE_RW (hence _PAGE_WRITE) +> is defined as 0 and _PAGE_RO must be set when the page in not writeable. > So that's a prerequisite to implementation of huge page > -> Patch 3, 4, 5 are prerequisits for the implementation of huge page=20 +> Patch 3, 4, 5 are prerequisits for the implementation of huge page > handling in the TLB miss handlers: -> * 3: for huge pages implementation we need to branch base of value of=20 +> * 3: for huge pages implementation we need to branch base of value of > bit 28 and 29 of the PGD entry. For this we need to preserve CR. -> * 4: With the instructions related to hugepages, there is not enough=20 -> space anymore in the TLB Exception areas, so part of the it has to be=20 +> * 4: With the instructions related to hugepages, there is not enough +> space anymore in the TLB Exception areas, so part of the it has to be > moved away. -> * 5: That one might be seen as not directly related to hugepages, but it= -=20 +> * 5: That one might be seen as not directly related to hugepages, but it > requires patch 3. > > Maybe I should reorder into 3, 4, 5, 2, 1, 6 ? diff --git a/a/content_digest b/N1/content_digest index b1bf2c0..43729d8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -15,7 +15,7 @@ "b\0" "christophe leroy <christophe.leroy@c-s.fr> writes:\n" "\n" - "> Le 14/08/2016 =C3=A0 16:27, Aneesh Kumar K.V a =C3=A9crit :\n" + "> Le 14/08/2016 \303\240 16:27, Aneesh Kumar K.V a \303\251crit :\n" ">> Christophe Leroy <christophe.leroy@c-s.fr> writes:\n" ">>\n" ">>> This set provides implementation of huge pages on the 8xx\n" @@ -32,20 +32,18 @@ ">> May be that can be sent as a separate series ?\n" ">>\n" ">\n" - "> Patch 2 is a lack in gup_hugepte: on 8xx, _PAGE_RW (hence _PAGE_WRITE)=20\n" - "> is defined as 0 and _PAGE_RO must be set when the page in not writeable.=\n" - "=20\n" + "> Patch 2 is a lack in gup_hugepte: on 8xx, _PAGE_RW (hence _PAGE_WRITE) \n" + "> is defined as 0 and _PAGE_RO must be set when the page in not writeable. \n" "> So that's a prerequisite to implementation of huge page\n" ">\n" - "> Patch 3, 4, 5 are prerequisits for the implementation of huge page=20\n" + "> Patch 3, 4, 5 are prerequisits for the implementation of huge page \n" "> handling in the TLB miss handlers:\n" - "> * 3: for huge pages implementation we need to branch base of value of=20\n" + "> * 3: for huge pages implementation we need to branch base of value of \n" "> bit 28 and 29 of the PGD entry. For this we need to preserve CR.\n" - "> * 4: With the instructions related to hugepages, there is not enough=20\n" - "> space anymore in the TLB Exception areas, so part of the it has to be=20\n" + "> * 4: With the instructions related to hugepages, there is not enough \n" + "> space anymore in the TLB Exception areas, so part of the it has to be \n" "> moved away.\n" - "> * 5: That one might be seen as not directly related to hugepages, but it=\n" - "=20\n" + "> * 5: That one might be seen as not directly related to hugepages, but it \n" "> requires patch 3.\n" ">\n" "> Maybe I should reorder into 3, 4, 5, 2, 1, 6 ?\n" @@ -56,4 +54,4 @@ "\n" -aneesh -d3f32ccee168844738570dd274562d75471b80977aa400a252c4586a2e1e7ecf +66cd2b3231a78a249c270675c0041fa2a1b4a071dc822161851a9a957b63c531
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.