From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A04C5C433F5 for ; Sun, 26 Sep 2021 06:44:20 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id C608160F9C for ; Sun, 26 Sep 2021 06:44:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org C608160F9C Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 0C23A6B0071; Sun, 26 Sep 2021 02:44:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 071E06B0072; Sun, 26 Sep 2021 02:44:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id EA1BC900002; Sun, 26 Sep 2021 02:44:18 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0084.hostedemail.com [216.40.44.84]) by kanga.kvack.org (Postfix) with ESMTP id DA4F16B0071 for ; Sun, 26 Sep 2021 02:44:18 -0400 (EDT) Received: from smtpin22.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 8C729180CE69C for ; Sun, 26 Sep 2021 06:44:18 +0000 (UTC) X-FDA: 78628785396.22.280C481 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by imf27.hostedemail.com (Postfix) with ESMTP id 6DA417000081 for ; Sun, 26 Sep 2021 06:44:17 +0000 (UTC) Received: from dggeml765-chm.china.huawei.com (unknown [172.30.72.56]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4HHGND5MX3zQk7q; Sun, 26 Sep 2021 14:39:56 +0800 (CST) Received: from huawei.com (10.175.101.6) by dggeml765-chm.china.huawei.com (10.1.199.175) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Sun, 26 Sep 2021 14:44:10 +0800 From: liuyuntao To: CC: , , , , , , , , Subject: Re: [PATCH v2] fix judgment error in shmem_is_huge() Date: Sun, 26 Sep 2021 14:42:01 +0800 Message-ID: <20210926064201.3416154-1-liuyuntao10@huawei.com> X-Mailer: git-send-email 2.30.0 In-Reply-To: <614538e2-16bb-2657-f374-64195c5c7c2@google.com> References: <614538e2-16bb-2657-f374-64195c5c7c2@google.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.175.101.6] X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To dggeml765-chm.china.huawei.com (10.1.199.175) X-CFilter-Loop: Reflected X-Rspamd-Queue-Id: 6DA417000081 X-Stat-Signature: jsx8q8aybjz5wo4tsx6a58xymbmzb5bx Authentication-Results: imf27.hostedemail.com; dkim=none; dmarc=pass (policy=none) header.from=huawei.com; spf=pass (imf27.hostedemail.com: domain of liuyuntao10@huawei.com designates 45.249.212.188 as permitted sender) smtp.mailfrom=liuyuntao10@huawei.com X-Rspamd-Server: rspam06 X-HE-Tag: 1632638657-328617 Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Sat, 25 Sep 2021, Hugh Dickins wrote: > On Fri, 24 Sep 2021, Hugh Dickins wrote: > > On Thu, 9 Sep 2021, Liu Yuntao wrote: > >=20 > > > In the case of SHMEM_HUGE_WITHIN_SIZE, the page index is not rounde= d > > > up correctly. When the page index points to the first page in a hug= e > > > page, round_up() cannot bring it to the end of the huge page, but > > > to the end of the previous one. > > >=20 > > > an example: > > > HPAGE_PMD_NR on my machine is 512(2 MB huge page size). > > > After allcoating a 3000 KB buffer, I access it at location 2050 KB. > >=20 > > Your example is certainly helpful, but weird! It's not impossible, > > but wouldn't it be easier to understand if you said "2048 KB" there? I wanted to emphasize that access to any bit in the first page will trigger this problem, so I didn't use "2048 KB". > >=20 > > > In shmem_is_huge(), the corresponding index happens to be 512. > > > After rounded up by HPAGE_PMD_NR, it will still be 512 which is > > > smaller than i_size, and shmem_is_huge() will return true. > > > As a result, my buffer takes an additional huge page, and that > > > shouldn't happen when shmem_enabled is set to within_size. > >=20 > > A colleague very recently opened my eyes to within_size on shmem_enab= led: > > I've always been dubious of both, but they can work quite well togeth= er. > >=20 > > >=20 > > > Fixes: f3f0e1d2150b2b ("khugepaged: add support of collapse for tmp= fs/shmem pages") > > > Signed-off-by: Liu Yuntao > >=20 > > Thanks, with a nice simplification from Kirill. > >=20 > > Acked-by: Hugh Dickins >=20 > Andrew has just sent this on to Linus - thanks - and that's fine: > no need to get in the way of that. >=20 > But since replying, I have remembered more history, and there is > something that we need to be aware of. >=20 > Whereas to you this is a straightforward off-by-one (or off-by-page) > fix, it also results in a significant change in behaviour - I'd say > usually for the better, but some might be surprised. This patch has > Kirill's Ack and my Ack, and I hope and believe that we can get away > with the change in behaviour: but let's be aware of it. >=20 > The change that concerns me is when, for example, copying a large > file into a huge=3Dwithin_size tmpfs (or more generally, just writing > to the file by appending at EOF in the usual way). >=20 > With the old WITHIN_SIZE code, the first 2MB was allocated in small > pages, then subsequent 2MB extents were allocated with huge pages; > including the final extent, even if it only needed a single byte. >=20 > I always thought that was very clunky behaviour, the small pages > coming at the wrong end of the file; and that's why I was dubious > about it as a sensible filesystem mount option. But I was under > the impression that it was the intended behaviour. >=20 > With your new WITHIN_SIZE code, all those appending allocations > are outside i_size, and the whole file is allocated in small pages. > (Then maybe later on khugepaged can assemble huge pages for it.) >=20 > Your patch makes within_size more sensible than it was for pre-sized > files (and I think it's fair to say that the majority of files in > shmem's internal mount, subject to thp/shmem_enabled, are likely to > be fixed-size files); and better-defined than it used to be on > growing files, but they won't get the huge pages they used to. Although my patch changes shmem's behaviour, it makes shmem consistent with the documentation. I think with the new code, it will be easier for our users to understand. >=20 > Hugh