kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: questions for Linus
Date: Tue, 31 May 2011 15:39:19 +0800	[thread overview]
Message-ID: <20110531073919.GA6099@kroah.com> (raw)
In-Reply-To: <BANLkTi=NzzX+yXb_dHFd8cXgb=65+BacQw@mail.gmail.com>

On Tue, May 31, 2011 at 02:12:36PM +0700, Mulyadi Santosa wrote:
> Hi Greg..
> 
> I came with these questions for Linus, hope you're kind enough to
> collect it and forward it to Linus in LinuxCon:
> 
> 1. When will Linux 2.8.x start? and what are the plans regarding the
> development model? do we back in dual 2.4.x/2.5x era? personally I
> think that model is nice.... makes one really know which tree to
> follow when he needs stable one, or the devel one...

This has been answered already.

> 2. I saw task/process scheduler is one that under heavy concern
> lately, take a look on "200 line patch that does wonder" for example.
> I am thinking, we better really incorporate pluggable scheduler
> framework, that enable us to change scheduling core algorithm on the
> fly. What do you think?

This has been covered many times by the scheduler developers already.
With cgroups, you can do lots of neat things already, no need to change
any kernel code.

> 3. I read somewhere that once Coverity helps Linux kernel developers
> found out unseen bugs using sophisticated static code analysis. Is
> that still happening now? Probably a good deal, squashing bugs in
> nowadays kernel's size is pretty hard, I could say..

I do not think Coverity is doing anything with the kernel anymore.  But
we have lots of other good code coverage tools that do static analysis
that people are using, and fixing bugs with today (sparse, coccinelle,
etc.)

But this is a good one, I'll try to work it into the questions, thanks,

greg k-h

  parent reply	other threads:[~2011-05-31  7:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  7:12 questions for Linus Mulyadi Santosa
2011-05-31  7:17 ` Stéphan Gorget
2011-05-31  7:19   ` Mulyadi Santosa
2011-05-31  7:39 ` Greg KH [this message]
2011-06-01  2:32   ` Pei Lin
2011-06-01  5:27     ` Greg KH
2011-05-31  8:40 ` Bernd Petrovitsch
2011-06-01  1:44 ` Greg KH
2011-06-01  2:12   ` Mulyadi Santosa
2011-06-01  6:40   ` nilesh
2011-06-01  7:02     ` Greg KH
2011-06-01  7:21       ` nilesh
2011-06-23  8:46         ` nilesh
2011-06-02  8:18       ` Javier Martinez Canillas

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=20110531073919.GA6099@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).