From: Karel Zak <kzak@redhat.com>
To: Davidlohr Bueso <dave@gnu.org>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: non-recursive build system
Date: Tue, 12 Jun 2012 17:18:19 +0200 [thread overview]
Message-ID: <20120612151819.GE23991@x2.net.home> (raw)
In-Reply-To: <1339505836.17574.6.camel@offworld>
On Tue, Jun 12, 2012 at 02:57:16PM +0200, Davidlohr Bueso wrote:
> On Tue, 2012-06-12 at 12:03 +0200, Karel Zak wrote:
> > * numbers (make -j)
> >
> > recursive | non-recursive
> > ----------+--------------
> > 2 cores: 14.5 sec | 13.2 sec
> > 16 cores: 9.5 sec | 4.3 sec
> >
> > (... more CPU cores means more fun;-)
>
> Nice, are these real cores or HT?
real cores, the machine with 16 cores was AMD from RH lab
Unfortunately I have no such machine at home. Any HW sponsor around? :-))
> > - rename fdisk/ to fdisks/
>
> fdisk-utils?
The ideal solution is to have libfdisk/ and then we can add small
fdisk.c, sfdisk.c and cfdisk.c files to disk-utils/. (See mount.c and
libmount/.)
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-06-12 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 10:03 non-recursive build system Karel Zak
2012-06-12 12:57 ` Davidlohr Bueso
2012-06-12 15:18 ` Karel Zak [this message]
2012-06-12 19:26 ` Davidlohr Bueso
2012-06-27 9:30 ` Karel Zak
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=20120612151819.GE23991@x2.net.home \
--to=kzak@redhat.com \
--cc=dave@gnu.org \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).