All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Thinking about Linux 4.0...
Date: Mon, 26 Jul 2004 15:20:02 -0400	[thread overview]
Message-ID: <41055962.1050002@techsource.com> (raw)

"4.0, you say?"  Well, the idea is to get people thinking about things 
which otherwise they might not suggest because they're just too outlandish.

With the embracing of this new development model, we will speed up Linux 
microevolution.  New features which are consistent with the philosophy 
of 2.6 will be accepted more readily.  But there will now be some added 
resistance against, shall we say, punctuations in the equillibrium. 
That is, revolutionary new ideas which break things or affect the 
philosophy of the kernel in a very fundamental way will be shunned.  The 
reason this is a problem is because, I expect, 2.6 will live longer as 
the bleeding edge than those that came before.

It might be interesting to see people discuss advances to the Linux 
kernel which, if interesting enough, would force a meaningful push into 
2.7.  And also interesting would be discussion of ideas that would be 
good for the kernel to have but which are too radical for 2.6.

Also, if you have an idea in reserve which you think would not work for 
2.6, you might be wrong.  It might be that some radical ideas could be 
made to fit.


Here's an example (probably a bad one):  Lots of discussion has been 
going on about reducing latency.  Many of the ideas just patch over the 
latencies, rather than, say, making it impossible to have latency 
problems.  Is there room in the future of Linux to have a driver model 
which is much more real-time in nature?


                 reply	other threads:[~2004-07-26 19:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41055962.1050002@techsource.com \
    --to=miller@techsource.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.