All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <zhangyifan46@huawei.com>
Cc: <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] an idea about parallel doing do_patch
Date: Mon, 7 Sep 2020 08:37:12 +0000	[thread overview]
Message-ID: <20200907083711.GL2026@korppu> (raw)
In-Reply-To: <iYPR.1599467249227446374.EQbU@lists.openembedded.org>

Hi,

On Mon, Sep 07, 2020 at 01:27:29AM -0700, zhangyifan46 via lists.openembedded.org wrote:
> In our peoject,we have suffered a lot from long duration of do_patch of linux kernel(3000+ patches). I found that one do_patch task uses only one process. So I modify a llittle do do_patch task. Here is my idea:
> 1.analyse the patches,only getting the modified files of each patch.
> 2.cluster all patches according to the files modified( patch no.1 modifies file A,B ,patch no.2 modifies file A, patch no.3 modifies file C,then we cluster patch no.1 and no.2 as  a group, patch no.3 as another group) , here I use union-find to do the cluster
> 3.assign one group on one process
> But I met the problem of probabilistic missing patches.
> Anyone has any comments about my idea?

I think having large patch sets in meta layers and applied with bitbake are not the
right solution. I would create a custom git repo and branch for large forks/branches
like this.

Possibly it could also be possible to apply patches with git through mbox files, but
I don't think this will much faster than bitbake.

Hope this helps,

-Mikko

> 

  reply	other threads:[~2020-09-07  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  8:27 an idea about parallel doing do_patch zhangyifan46
2020-09-07  8:37 ` Mikko Rapeli [this message]
     [not found]   ` <20610.1599468217725892636@lists.openembedded.org>
2020-09-07  8:58     ` [bitbake-devel] " Mikko Rapeli
2020-09-07 10:30       ` Richard Purdie
2020-09-09 23:25   ` Khem Raj

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=20200907083711.GL2026@korppu \
    --to=mikko.rapeli@bmw.de \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=zhangyifan46@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.