From: Jeff King <peff@peff.net>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Jacob Keller" <jacob.keller@gmail.com>,
"Git mailing list" <git@vger.kernel.org>
Subject: Re: [PATCH v3] coccicheck: process every source file at once
Date: Fri, 5 Oct 2018 12:59:01 -0400 [thread overview]
Message-ID: <20181005165901.GE11254@sigill.intra.peff.net> (raw)
In-Reply-To: <02874ECE860811409154E81DA85FBB5884CCBED2@ORSMSX115.amr.corp.intel.com>
On Fri, Oct 05, 2018 at 04:53:35PM +0000, Keller, Jacob E wrote:
> > Are we OK with saying 1.3-1.8GB is necessary to run coccicheck? That
> > doesn't feel like an exorbitant request for a developer-only tool these
> > days, but I have noticed some people on the list tend to have lousier
> > machines than I do. ;)
> >
> > -Peff
>
> It's probably not worth trying to make this more complicated and scale
> up how many files we do at once based on the amount of available
> memory on the system...
Yeah, that sounds too complicated. At most I'd give a Makefile knob to
say "spatch in batches of $(N)". But I'd prefer to avoid even that
complexity if we can.
-Peff
next prev parent reply other threads:[~2018-10-05 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 20:07 [PATCH v3] coccicheck: process every source file at once Jacob Keller
2018-10-02 20:18 ` Jacob Keller
2018-10-05 2:17 ` Jacob Keller
2018-10-05 12:40 ` SZEDER Gábor
2018-10-05 16:25 ` Jeff King
2018-10-05 16:53 ` Keller, Jacob E
2018-10-05 16:59 ` Jeff King [this message]
2018-10-05 18:50 ` SZEDER Gábor
2018-10-05 19:00 ` Jeff King
2018-10-05 23:10 ` Jacob Keller
2018-10-06 8:42 ` René Scharfe
2018-10-09 3:11 ` Jeff King
2018-10-05 18:39 ` SZEDER Gábor
2018-10-05 19:02 ` Jeff King
2018-10-05 19:54 ` SZEDER Gábor
2018-10-09 3:15 ` Jeff King
2018-10-10 11:44 ` SZEDER Gábor
2018-10-10 13:59 ` Jeff King
2018-10-07 11:36 ` Beat Bolli
2018-10-07 11:49 ` Beat Bolli
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181005165901.GE11254@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jacob.keller@gmail.com \
--cc=szeder.dev@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).