Received: by 2002:a5d:9c59:0:0:0:0:0 with SMTP id 25csp274917iof; Mon, 6 Jun 2022 03:17:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwzfQqFVQEsCeM8Hk6uLsbiGlracybpK69Q8xMunJWtI4fkTQBVqzK63Dm9UjvyOZs8gOg2 X-Received: by 2002:a17:90b:3b88:b0:1e6:7aa2:4301 with SMTP id pc8-20020a17090b3b8800b001e67aa24301mr25629284pjb.118.1654510673268; Mon, 06 Jun 2022 03:17:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654510673; cv=none; d=google.com; s=arc-20160816; b=gsiwzEjfbDITw7VKrdiLuSYDsG+mZKfpRP+e41PYKlg0g97EUw1jeSiqsLKZi8858f hdFyKmbMIPr4XcujN80LSkhDsOJLptp5HiwpPaPRgFwCKp8637njVAx31lUW4IQ3nzzS +/sEInWPTYisthmfZPfE5pAiS//RYcu94W9gpg7jO0W0SnlPGhakO/PjZRriD7WiFjSU vkqCd20X/lp4wQfk4js65ZpIwW5Poo0fJW/2BjXsUPA9H7bwgn/1735epjsRpFgALEpU LrgGzVsfxlPhXHxC8TxSNkupth5a4f9vXx0xw1w4GdeUyejASWoNjUjMQXuKlVDqVAzK tyEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=Wl/4+gqlRIpnZ9afydR1MhherCCAEwCFrXnlIDnjQZI=; b=SXeVgytJhOyhedgf5+kJoFByrnVzL0WRxXXVhL3MBQToZHfmIcRqN9Hn9xey6bXcXy 9W9HnOZKo0i4DN0DAwUz374nptC6a7LpWGTZf9gVsTSyw4musTGYgKJgzPH39mV3epga PdeMN5D1q73Mj8NQPit7VyxCuNjOh4qg54HXVof6RLPHGkI58pmvwvPMtmz8msWh9lup J1nTceCxecSwJBm63RhbE6fnehZXvn3nYFcsLCO2uHypaxPGRwuk0ijHQYvHLgywECQQ iBpRULg6yJlMhlxR7nu3CMxar5ZoKeuM4es7ibG9f0pck52pjAVL4rqLA/vkQvT046mr mVeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=gggJDu+J; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id x14-20020a63170e000000b003fae900c345si18775640pgl.183.2022.06.06.03.17.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Jun 2022 03:17:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=gggJDu+J; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id A4CE511AFF6; Mon, 6 Jun 2022 02:56:27 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233270AbiFFJ4Q (ORCPT + 99 others); Mon, 6 Jun 2022 05:56:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39004 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233253AbiFFJ4O (ORCPT ); Mon, 6 Jun 2022 05:56:14 -0400 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3C5B6118D25 for ; Mon, 6 Jun 2022 02:56:12 -0700 (PDT) Received: by mail-ej1-x62d.google.com with SMTP id q1so27867164ejz.9 for ; Mon, 06 Jun 2022 02:56:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wl/4+gqlRIpnZ9afydR1MhherCCAEwCFrXnlIDnjQZI=; b=gggJDu+JblfDexfqcK5EaRvBHEqC12bcsI/OlR26sqffk9I4lIK2wk0Ul8QiNM7Baq Fieg7hFeEhmAAWZSo5/mi8AuffEQv7oV6zZH4i4SM8quF8/y9ztI++gAy1Ce7nwZ/Qh/ moR+aEqMqt0mD/WUx1z0U527rCJ0a1qvgV6fU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wl/4+gqlRIpnZ9afydR1MhherCCAEwCFrXnlIDnjQZI=; b=rbR9KuwM/2NdgrDugd0URJEqxF2UT0BnXfWIce+mLmoq8CZx4w3qOv/hEAfUQwEMYy i3IZU+BFVNLbvxNxGj6lOYSNB6W9x39XDFONv1DxNtFTXsjsPrlZ3QqWAc2MFmiQdIQb CZuGsPtGCXu9fD87FEtP6Opj1rZwyqP/oBf0I3754ob0gezfiudL0t4KDoDgjGLMaQbx +cgxv3JdTfciaye0nEDttkrr5XAxE7wSoQdW1N6e0SFQOotx5n1QJrvN1hMPkZhGllhi JJWMa+Cl+rQuhWGBDE0SaS6fRINEi+Wjxp2XPp7tEi2uL0c7vRVZLohVFqmFXSutVpfZ isyQ== X-Gm-Message-State: AOAM531UtX7KrWtOMIyxSSjmBUZLKsLL/XFy96lp1j6uWOnKU4zeZKgh lzjojk7ibtY66EurRFo1aNIRbrO9hyqvGBrCJO3nVn0UZIk= X-Received: by 2002:a17:906:99ca:b0:711:bdca:b85a with SMTP id s10-20020a17090699ca00b00711bdcab85amr6902624ejn.224.1654509370576; Mon, 06 Jun 2022 02:56:10 -0700 (PDT) MIME-Version: 1.0 References: <20220601103922.1338320-1-hsinyi@chromium.org> <20220601103922.1338320-4-hsinyi@chromium.org> <90b228ea-1b0e-d2e8-62be-9ad5802dcce7@samsung.com> <0e84fe64-c993-7f43-ca52-8fee735b0372@squashfs.org.uk> In-Reply-To: <0e84fe64-c993-7f43-ca52-8fee735b0372@squashfs.org.uk> From: Hsin-Yi Wang Date: Mon, 6 Jun 2022 17:55:44 +0800 Message-ID: Subject: Re: [PATCH v4 3/3] squashfs: implement readahead To: Phillip Lougher Cc: Marek Szyprowski , Matthew Wilcox , Xiongwei Song , Zheng Liang , Zhang Yi , Hou Tao , Miao Xie , Andrew Morton , "linux-mm @ kvack . org" , "squashfs-devel @ lists . sourceforge . net" , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 6, 2022 at 11:54 AM Phillip Lougher wrote: > > On 03/06/2022 16:58, Marek Szyprowski wrote: > > Hi Matthew, > > > > On 03.06.2022 17:29, Matthew Wilcox wrote: > >> On Fri, Jun 03, 2022 at 10:55:01PM +0800, Hsin-Yi Wang wrote: > >>> On Fri, Jun 3, 2022 at 10:10 PM Marek Szyprowski > >>> wrote: > >>>> Hi Matthew, > >>>> > >>>> On 03.06.2022 14:59, Matthew Wilcox wrote: > >>>>> On Fri, Jun 03, 2022 at 02:54:21PM +0200, Marek Szyprowski wrote: > >>>>>> On 01.06.2022 12:39, Hsin-Yi Wang wrote: > >>>>>>> Implement readahead callback for squashfs. It will read datablocks > >>>>>>> which cover pages in readahead request. For a few cases it will > >>>>>>> not mark page as uptodate, including: > >>>>>>> - file end is 0. > >>>>>>> - zero filled blocks. > >>>>>>> - current batch of pages isn't in the same datablock or not enough in a > >>>>>>> datablock. > >>>>>>> - decompressor error. > >>>>>>> Otherwise pages will be marked as uptodate. The unhandled pages will be > >>>>>>> updated by readpage later. > >>>>>>> > >>>>>>> Suggested-by: Matthew Wilcox > >>>>>>> Signed-off-by: Hsin-Yi Wang > >>>>>>> Reported-by: Matthew Wilcox > >>>>>>> Reported-by: Phillip Lougher > >>>>>>> Reported-by: Xiongwei Song > >>>>>>> --- > >>>>>> This patch landed recently in linux-next as commit 95f7a26191de > >>>>>> ("squashfs: implement readahead"). I've noticed that it causes serious > >>>>>> issues on my test systems (various ARM 32bit and 64bit based boards). > >>>>>> The easiest way to observe is udev timeout 'waiting for /dev to be fully > >>>>>> populated' and prolonged booting time. I'm using squashfs for deploying > >>>>>> kernel modules via initrd. Reverting aeefca9dfae7 & 95f7a26191deon on > >>>>>> top of the next-20220603 fixes the issue. > >>>>> How large are these files? Just a few kilobytes? > >>>> Yes, they are small, most of them are smaller than 16KB, some about > >>>> 128KB and a few about 256KB. I've sent a detailed list in private mail. > >>>> > >>> Hi Marek, > >>> > >>> Are there any obvious squashfs errors in dmesg? Did you enable > >>> CONFIG_SQUASHFS_FILE_DIRECT or CONFIG_SQUASHFS_FILE_CACHE? > >> I don't think it's an error problem. I think it's a short file problem. > >> > >> As I understand the current code (and apologies for not keeping up > >> to date with how the patch is progressing), if the file is less than > >> msblk->block_size bytes, we'll leave all the pages as !uptodate, leaving > >> them to be brough uptodate by squashfs_read_folio(). So Marek is hitting > >> the worst case scenario where we re-read the entire block for each page > >> in it. I think we have to handle this tail case in ->readahead(). > > > > I'm not sure if this is related to reading of small files. There are > > only 50 modules being loaded from squashfs volume. I did a quick test of > > reading the files. > > > > Simple file read with this patch: > > > > root@target:~# time find /initrd/ -type f | while read f; do cat $f > > >/dev/null; done > > > > real 0m5.865s > > user 0m2.362s > > sys 0m3.844s > > > > Without: > > > > root@target:~# time find /initrd/ -type f | while read f; do cat $f > > >/dev/null; done > > > > real 0m6.619s > > user 0m2.112s > > sys 0m4.827s > > > > It has been a four day holiday in the UK (Queen's Platinum Jubilee), > hence the delay in responding. > > The above read use-case is sequential (only one thread/process), > whereas the use-case where the slow-down is observed may be > parallel (multiple threads/processes entering Squashfs). > > The above sequential use-case if the small files are held in > fragments, will be exhibiting caching behaviour that will > ameliorate the case where the same block is being repeatedly > re-read for each page in it. Because each time > Squashfs is re-entered handling only a single page, the > decompressed block will be found in the fragment > cache, eliminating a block decompression for each page. > > In a parallel use-case the decompressed fragment block > may be being eliminated from the cache (by other reading > processes), hence forcing the block to be repeatedly > decompressed. > > Hence the slow-down will be much more noticable with a > parallel use-case than a sequential use-case. It also may > be why this slipped through testing, if the test cases > are purely sequential in nature. > > So Matthew's previous comment is still the most likely > explanation for the slow-down. > Thanks for the pointers. To deal with short file cases (nr_pages < max_pages), Can we refer to squashfs_fill_page() used in squashfs_read_cache(), similar to the case where there are missing pages on the block? Directly calling squashfs_read_data() on short files will lead to crash: Unable to handle kernel paging request at virtual address: [ 19.244654] zlib_inflate+0xba4/0x10c8 [ 19.244658] zlib_uncompress+0x150/0x1bc [ 19.244662] squashfs_decompress+0x6c/0xb4 [ 19.244669] squashfs_read_data+0x1a8/0x298 [ 19.244673] squashfs_readahead+0x2cc/0x4cc I also noticed that the function didn't set flush_dcache_page() with SetPageUptodate() previously. Put these 2 issues together: diff --git a/fs/squashfs/file.c b/fs/squashfs/file.c index 658fb98af0cd..27519f1f9045 100644 --- a/fs/squashfs/file.c +++ b/fs/squashfs/file.c @@ -532,8 +532,7 @@ static void squashfs_readahead(struct readahead_control *ractl) if (!nr_pages) break; - if (readahead_pos(ractl) >= i_size_read(inode) || - nr_pages < max_pages) + if (readahead_pos(ractl) >= i_size_read(inode)) goto skip_pages; index = pages[0]->index >> shift; @@ -548,6 +547,23 @@ static void squashfs_readahead(struct readahead_control *ractl) if (bsize == 0) goto skip_pages; + if (nr_pages < max_pages) { + struct squashfs_cache_entry *buffer; + + buffer = squashfs_get_datablock(inode->i_sb, block, + bsize); + if (!buffer->error) { + for (i = 0; i < nr_pages && expected > 0; i++, + expected -= PAGE_SIZE) { + int avail = min_t(int, expected, PAGE_SIZE); + + squashfs_fill_page(pages[i], buffer, i * PAGE_SIZE, avail); + } + } + squashfs_cache_put(buffer); + goto skip_pages; + } + res = squashfs_read_data(inode->i_sb, block, bsize, NULL, actor); @@ -564,8 +580,10 @@ static void squashfs_readahead(struct readahead_control *ractl) kunmap_atomic(pageaddr); } - for (i = 0; i < nr_pages; i++) + for (i = 0; i < nr_pages; i++) { + flush_dcache_page(pages[i]); SetPageUptodate(pages[i]); + } } > Phillip > > > Best regards >