Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Tiberiu A Georgescu <tiberiu.georgescu@nutanix.com>
To:     akpm@linux-foundation.org, corbet@lwn.net, peterx@redhat.com,
        david@redhat.com, linux-doc@vger.kernel.org, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org
Cc:     ivan.teterevkov@nutanix.com, florian.schmidt@nutanix.com,
        carl.waldspurger@nutanix.com, jonathan.davies@nutanix.com,
        Tiberiu A Georgescu <tiberiu.georgescu@nutanix.com>
Subject: [PATCH v2 0/1] Documenting shmem as an exception case for the pagemap
Date:   Mon, 20 Sep 2021 16:49:30 +0000
Message-Id: <20210920164931.175411-1-tiberiu.georgescu@nutanix.com>
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?MB/WGb8mnUqDgzvc62UhqDssa1clLh6aOcLVCZ3dE2Tm/tcxeLRRjrJq95NG?=
 =?us-ascii?Q?fJbUQmPfK4iZvfDkr8EHAUuco9b3EMUagHIOcMaRSs5kr7R4O9g4wb26NDQo?=
 =?us-ascii?Q?S68I5V9H+8bb9vyAcwlxL/CNhmnE9cvalGTGS4cy7sLcMxZ3A/ppgnHOtIc4?=
 =?us-ascii?Q?9TzDc4X7ieN4UmSZRZhfvtnhE/xobZeFp86lzPPq8TNCX5rKUAQHcD7u9/kM?=
 =?us-ascii?Q?72dz3ajEaVRofrzVWOr5uWHmPsi0JdgAuiPjmejJoCUy7YHruZXRSsbdLjCW?=
 =?us-ascii?Q?XNa9HA9qFw/L0gsSbbjmTAPfl5ZjnrOlyPg5xYZeEj7KIn3eJ9Q+ItlqiM4y?=
 =?us-ascii?Q?HILFi1rxQhRKoCQwpCVKBxc1yk5j+MgPJhH0JthhmyYtzGV7KcM+jR3z5/AT?=
 =?us-ascii?Q?iRqJvKVpen7gatAInLaBwxhws51OnCb5jvAnFUWSYn+JOKXDBm3M9kXcQVGC?=
 =?us-ascii?Q?O6Hy4sP0mA7AtymQ0JQTb92ov6DquS80AcU39BEtEKNmLaNzZyrUd6xdrujI?=
 =?us-ascii?Q?5uKQsxM6BiLn5XDJAeJO/SwnrJtqi13shWzSsy1oYfumkajXg08WaaZsJ/B3?=
 =?us-ascii?Q?JsoLswfSNieG3es4qvsHbG9KoICWLBfr35lc2bUC4zIATXJTWnEjD3d5IVEg?=
 =?us-ascii?Q?SShNndn6jMheE3J5iyWgJUsAd2ThHfsyFKScPNCaAclVmgN8DCYwQs45l09/?=
 =?us-ascii?Q?t+g3dVG3HxW3EGqeFRh+Dylx2drHj4qFE0q8BspxSmsc58gMFfkc7+OGzwad?=
 =?us-ascii?Q?VNUZG7SBgLqCQYjjpCrckGEVHRQD7uzRPKrcg6AIKBstDeof9mU4wmTM+xas?=
 =?us-ascii?Q?nF/XehM95WEoYGaqVVbRKsgwwIFCUklujNa1tsDMBMQTA9Esosx4zcme8Lz4?=
 =?us-ascii?Q?LGk0WCWJrWRnTTYkXOIHEXc4B7VQSMY7gt63jMRRvN6DWfpDJ345SZ7l1ouJ?=
 =?us-ascii?Q?XBdFWXVYNiCFiQm/dhqBtGSfKyM0m7uFHaOXWiZz3EkOzH3QQHaFkCh592wH?=
 =?us-ascii?Q?4Yjc3tC5vdZTLrdXGHJk4gG8xcqGgDTIpi30MzEmTZ6J5PlsS5qtDeH5y9A4?=
 =?us-ascii?Q?APUAscj96btBBAn8MyvY0WqvvsVq1YImtmUHOdZMKW0XKuoSpOhO4U8htKKA?=
 =?us-ascii?Q?apDfmIdZRGuuv/RC5+x04lP+nEyF+DtHQrMw3Vbd1TDiQrKJTKZGiPZtcTkH?=
 =?us-ascii?Q?O+jP5fE9XTIhb9spoMyuGdz77nNgpOAireRsO4BBE74PyW+dE8Mvk6QYyUeM?=
 =?us-ascii?Q?d4Iai8IF3ffZJsjUZJAfLOeCkwiweu11r8SNZtYReUmo4Gg1P4Y+YdKDVxIL?=
 =?us-ascii?Q?jKzi7gjY5AVQwO2IXQVvHehD?=
X-OriginatorOrg: nutanix.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8637d80e-1492-4c7e-1816-08d97c56a4db
X-MS-Exchange-CrossTenant-AuthSource: DM6PR02MB5578.namprd02.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Sep 2021 16:49:42.5858
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: bb047546-786f-4de1-bd75-24e5b6f79043
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: CrDPZSMlIWXwxosu7ciysjPtNH5wjV0DZqDyiu1S00K0vqi6kmi6Cb3dQnxFSR4S4row4hhq3w+OxjrKpnfhVb/zJwn3bU74ulAGA3a5hjQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR02MB6953
X-Proofpoint-GUID: DGnDJnLsIqyTQ3h3Q2SmQWgkTDdpRXO-
X-Proofpoint-ORIG-GUID: DGnDJnLsIqyTQ3h3Q2SmQWgkTDdpRXO-
X-Proofpoint-Virus-Version: vendor=baseguard
 engine=ICAP:2.0.182.1,Aquarius:18.0.790,Hydra:6.0.391,FMLib:17.0.607.475
 definitions=2021-09-20_07,2021-09-20_01,2020-04-07_01
X-Proofpoint-Spam-Reason: safe
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

This patch follows the discussions on a previous documentation patch
thread [1]. It presents the exception case of shared memory management from
the pagemap's point of view. It briefly describes what is missing, why it
is missing and alternatives to the pagemap for swap info retrieval.

In short, the kernel does not keep track of PTEs for shared pages within
the processes that references them. Thus, the proc/pid/pagemap tool cannot
print the swap destination of the shared memory pages, instead setting the
pagemap entry to zero for both non-allocated and swapped out pages. This
can create confusion for users who need information on swapped out pages.

The reasons why maintaining the PTEs of all swapped out shared pages among
all processes while maintaining similar performance is not a trivial task,
or a desirable change have been discussed extensively [1][2][3][4]. There
are also arguments for why this arguably missing information should be
exposed to the user in either a future pagemap patch, or an alternative.

[1]: https://marc.info/?m=162878395426774
[2]: https://lore.kernel.org/lkml/20210730160826.63785-1-tiberiu.georgescu@nutanix.com/
[3]: https://lore.kernel.org/lkml/20210807032521.7591-1-peterx@redhat.com/
[4]: https://lore.kernel.org/lkml/20210715201651.212134-1-peterx@redhat.com/

Kind regards,
Tibi

Tiberiu A Georgescu (1):
  Documentation: update pagemap with shmem exceptions

 Documentation/admin-guide/mm/pagemap.rst | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

-- 
2.33.0.363.g4c719308ce