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 X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 78136C04A6B for ; Mon, 6 May 2019 17:54:15 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3A7272053B for ; Mon, 6 May 2019 17:54:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="FQ9q2aM/" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3A7272053B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1hNhoa-0004ad-VE for kernelnewbies@archiver.kernel.org; Mon, 06 May 2019 13:54:12 -0400 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1hNhn2-0002Mc-8g for kernelnewbies@kernelnewbies.org; Mon, 06 May 2019 13:52:36 -0400 Received: by mail-lj1-x22a.google.com with SMTP id h21so11820868ljk.13 for ; Mon, 06 May 2019 10:52:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Y6A6wdPRHyTrqksriNIFNmnyKpo9wAn8awvy1d1JyV4=; b=FQ9q2aM/j6UKmsBoOYq0RaTGpTKvXjcLSbTDQDdYSs/9VSnxFeKmTKeAPe/z+2ncwf FqynuI9uVn7LwQ2wzc+H+28EXUOu23QR2GRNg+Tayi+MIeUzog4TfXECB/e5EExCimB2 Q5ifoHyiQG6sUpqT3ErXsgluzsROGZUYgGrZbju0LgdYSGEDabNFsox0stmQaeKPzPyi 2Ba1ac+Ie+0KJtK8zp4UM8yqM+I56kb8ubB+wrvCU3z6aBaeopPYjoflgzIxv9LTjb+N jg4MztbnKCZ2AZZa3mRtfh/oJdFOvVYMC0zcE1b3+JJWzi5li0toBFboipKcqEPdzKEK YNAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Y6A6wdPRHyTrqksriNIFNmnyKpo9wAn8awvy1d1JyV4=; b=CSxEeTz8Z/UfouoAkQ66NXt5xGlvdGBcft0Fjms80a/MOJCTEru7m2kGgs+y8RQ2D8 DIcaLYsLOooPbfttJ89VaxTfH0HhLVS2ti/+BNdnh2/8XYbQ8y48UnGT5joDSde9VbC6 dEw9HzV8dhVBcZa3/C2qxO9vcOIMUFvvmEkP3FtXVwkdv8JYXhXx8bbFZ1s8G+FrNepl Z8NhUzVXmSk+SRcQg4l3o+Gdm/wMTmdE/AzxazL7qFuu9BSe+PonPRoFWCTrDDO4Fn3m olxdcomZoewh3pMccsuEBHR8K3FPxDMHLuLjLp1dVic5rGTgredsr75GJ9R2eRVH+t6L witw== X-Gm-Message-State: APjAAAVuBlAbUVKm7Qsj/n/ntU/fyjzyAVsm+IEXboSTCR1e9JaKuf4y 0eWn1M4eJobcc98z/brbo8LuPJSthFnydelijvGCJpQ04ew= X-Google-Smtp-Source: APXvYqzCdF/M2bzjXS/ajgkAtK03/wQe04bdqwYpmEztfkYRNZzcbCOmBqacKgsPw/RzpOLnxeLIKSQzqxNQhjSfcIQ= X-Received: by 2002:a2e:89da:: with SMTP id c26mr14057394ljk.186.1557165093246; Mon, 06 May 2019 10:51:33 -0700 (PDT) MIME-Version: 1.0 From: Probir Roy Date: Mon, 6 May 2019 12:51:21 -0500 Message-ID: Subject: locality of extent status tree traversal To: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org Hi, I am running Phoronix-fio benchmark on Linux kernel 4.18.0-rc5. I observe the same nodes have been traversed on the extent status tree in "ext4_es_lookup_extent" function when ext4 write begins. What's the locality signature of ext4_es_lookup_extent? Is it possible that same logical block being looked up repeatedly (Temporal)? Is it possible that co-located logical blocks are searched by ext4_es_lookup_extent (spatial)? -- Probir Roy _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies