public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philippe Elie <phil.el@wanadoo.fr>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Rik van Riel <riel@surriel.com>, linux-kernel@vger.kernel.org
Subject: Re: WANTED: kernel projects for CS students
Date: Mon, 15 Oct 2007 18:31:54 +0200	[thread overview]
Message-ID: <20071015163154.GA2884@zaniah> (raw)
In-Reply-To: <20071015142352.GA21259@uranus.ravnborg.org>

On Mon, 15 Oct 2007 at 16:23 +0000, Sam Ravnborg wrote:

> Hi Rik.
> 
> On Sun, Oct 14, 2007 at 07:01:28PM -0400, Rik van Riel wrote:
> > The kernel newbies community often gets inquiries from CS students who
> > need a project for their studies and would like to do something with
> > the Linux kernel, but would also like their code to be useful to the
> > community afterwards.
> > 

... 

> Increase speed for a build with no updates
> ==========================================
> On a resonably fast machine with a decent config it takes
> roughly 10 seconds to do a make where nothing is updated.
> Generating one single Makefile is assumed to speed up things
> and will in addition allow a simpler syntax as what is used today
> for some of the uglier constructs.
> 
> Contact: Sam Ravnborg <sam@ravnborg.org>
> Difficulty: 5
> Language: Perl or C

Isn't make -j 2 or more implemented by running multiple make in sub-dirs ?
Parallel make is more and more used even on cheap hardware.

-- 
Phe


  parent reply	other threads:[~2007-10-15 16:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 23:01 WANTED: kernel projects for CS students Rik van Riel
2007-10-15 10:40 ` WANG Cong
2007-10-15 17:13   ` Rik van Riel
2007-10-15 14:23 ` Sam Ravnborg
2007-10-15 15:10   ` Rik van Riel
2007-10-15 18:31     ` Sam Ravnborg
2007-10-15 16:31   ` Philippe Elie [this message]
2007-10-15 16:36     ` Philippe Elie
2007-10-15 16:52       ` Jan Engelhardt
2007-10-15 16:53       ` Xavier Bestel
2007-10-15 18:19     ` Sam Ravnborg
2007-10-15 15:40 ` Jörn Engel
2007-10-15 17:04 ` Doug Whitesell (LKML)
2007-10-15 17:04 ` Mark Gross
2007-10-15 18:30   ` Sam Ravnborg
2007-10-15 18:45     ` Mark Gross
2007-10-15 19:54     ` Giacomo Catenazzi
2007-10-16 20:06       ` Mark Gross
2007-10-16 20:09         ` Jan Engelhardt
2007-10-16 20:23           ` Rik van Riel
2007-10-16 20:25             ` Jan Engelhardt
2007-10-16 21:10               ` david
2007-10-16 21:30             ` david
2007-11-02  7:54             ` Giacomo Catenazzi
2007-10-16 20:31           ` Giacomo Catenazzi
2007-10-15 19:17   ` Alexey Dobriyan
2007-10-15 19:54     ` Folkert van Heusden
2007-10-16 20:10     ` Mark Gross
2007-10-16  0:39   ` david
2007-10-15 17:10 ` Zan Lynx
2007-10-15 17:23   ` Rik van Riel
2007-10-16  0:51   ` david
2007-10-15 17:30 ` Guilherme Amadio
2007-10-15 18:03   ` J. Bruce Fields
2007-10-17 17:45 ` Mark Gross
2007-10-18  4:51 ` Toshiharu Harada
2007-10-28 18:07 ` Pavel Machek
2007-10-28 18:57   ` Rafael J. Wysocki
2007-10-29 19:48   ` Lennart Sorensen
2007-10-29 20:19     ` Pavel Machek
2007-10-29 21:44       ` Lennart Sorensen
2007-11-03  3:08         ` Valdis.Kletnieks
2007-11-03  3:36           ` Rik van Riel
2007-11-03  9:44             ` Wander Winkelhorst
2007-11-03 10:05             ` david

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=20071015163154.GA2884@zaniah \
    --to=phil.el@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@surriel.com \
    --cc=sam@ravnborg.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