From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: questions for Linus
Date: Tue, 31 May 2011 14:12:36 +0700 [thread overview]
Message-ID: <BANLkTi=NzzX+yXb_dHFd8cXgb=65+BacQw@mail.gmail.com> (raw)
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...
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?
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..
that's all for now Greg...thanks in advance...hopefully it's still make it..
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next reply other threads:[~2011-05-31 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 7:12 Mulyadi Santosa [this message]
2011-05-31 7:17 ` questions for Linus Stéphan Gorget
2011-05-31 7:19 ` Mulyadi Santosa
2011-05-31 7:39 ` Greg KH
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='BANLkTi=NzzX+yXb_dHFd8cXgb=65+BacQw@mail.gmail.com' \
--to=mulyadi.santosa@gmail.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).