public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 07/15] kern-tools: integrate ZFS speedup patch
Date: Fri, 18 Nov 2022 17:28:51 -0500	[thread overview]
Message-ID: <cbbab79f03da7078715faeb89595555cff454912.1668810409.git.bruce.ashfield@gmail.com> (raw)
In-Reply-To: <cover.1668810409.git.bruce.ashfield@gmail.com>

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Bumping the SRCREV to integrat the following kern-tools change:

   commit 2d01f24bc78256c709728eb3f204491bce13e0e5
   Author: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
   Date:   Fri Nov 4 23:32:38 2022 +0000

       kconf_check: store some files in tmpdir

       Some file systems, like ZFS, are very slow at appending to existing
       files. Due to Copy-On-Write nature, they create a new copy of a file
       each time we do ">>" in a shell script. This becomes very noticeable
       if shell script does lots and lots of appends, like sanitize_fragment()
       function in kconf_check. On my setup, do_kernel_configcheck task takes
       literally hours to complete.

       To fix this issue, we can store sanitized_list and fragment_errors.txt
       files on tmpfs, which is extremely fast at writing. As most distros
       use tmpfs for /tmp, logical step is to use `mktemp` to create
       temporary files.

       After completing writing to temporary locations, we can move those two
       files back to ${LOGDIR}.

       Also, function 'cleanup' was added to remove temporary files in case
       of abnormal exit.

       With this patch, do_kernel_configcheck task completes in ~2 minutes on
       my setup, which is a great improvement.

       Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 07d7daf5fb..12f1cf516e 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "\
 
 DEPENDS = "git-native"
 
-SRCREV = "6a4752ebbe7d242c02b3c74a5772926edd243626"
+SRCREV = "2d01f24bc78256c709728eb3f204491bce13e0e5"
 PV = "0.3+git${SRCPV}"
 
 inherit native
-- 
2.19.1



  parent reply	other threads:[~2022-11-18 22:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 22:28 [PATCH 00/15][v2] kernel: consolidated pull request bruce.ashfield
2022-11-18 22:28 ` [PATCH 01/15] linux-yocto-dev: bump to v6.0+ bruce.ashfield
2022-11-18 22:28 ` [PATCH 02/15] linux-yocto/5.19: update to v5.19.16 bruce.ashfield
2022-11-18 22:28 ` [PATCH 03/15] linux-yocto/5.15: update to v5.15.74 bruce.ashfield
2022-11-18 22:28 ` [PATCH 04/15] linux-yocto/5.19: update to v5.19.17 bruce.ashfield
2022-11-18 22:28 ` [PATCH 05/15] linux-yocto/5.15: update to v5.15.76 bruce.ashfield
2022-11-18 22:28 ` [PATCH 06/15] linux-yocto/5.19: cfg: intel and vesa updates bruce.ashfield
2022-11-18 22:28 ` bruce.ashfield [this message]
2022-11-18 22:28 ` [PATCH 08/15] linux-yocto-dev: bump to v6.1 bruce.ashfield
2022-11-18 22:28 ` [PATCH 09/15] kernel-devsrc: fix for v6.1+ bruce.ashfield
2022-11-18 22:28 ` [PATCH 10/15] lttng-modules: fix build " bruce.ashfield
2022-11-18 22:28 ` [PATCH 11/15] linux-yocto/5.19: security.cfg: remove configs which have been dropped bruce.ashfield
2022-11-18 22:28 ` [PATCH 12/15] linux-yocto/5.15: update to v5.15.78 bruce.ashfield
2022-11-18 22:28 ` [PATCH 13/15] linux-yocto/5.19: fix CONFIG_CRYPTO_CCM mismatch warnings bruce.ashfield
2022-11-18 22:28 ` [PATCH 14/15] linux-yocto/5.15: " bruce.ashfield
2022-11-18 22:28 ` [PATCH 15/15] linux-yocto/5.19: fix elfutils run-backtrace-native-core ptest failure bruce.ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cbbab79f03da7078715faeb89595555cff454912.1668810409.git.bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox