From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Ingo Molnar <mingo@kernel.org>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2 0/8] scheduler tinification
Date: Thu, 8 Jun 2017 19:14:29 +0100 [thread overview]
Message-ID: <20170608191429.2e454aa9@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20170608075936.426zbwb63drsemgh@gmail.com>
> As users ask for more features the the hardware capabilities will increase
> dramatically and home-grown microcontroller derived code plus minimal OSes will be
> replaced by a 'real' OS. Because both developers and users will demand IPv6
> compatibility, or Bluetooth connectivity, or storage support, or any random range
> of features we have in the Linux kernel.
There are already tiny OS's with that feature set but they don't feel
Unixish and aren't quite so fun to program.
> Even taking the 1MB size at face value (which I don't: a networking enabled system
> can probably not function very well with just 1MB of RAM) - the RAM-starved 1 MB
> system today will effectively be a 2 MB system in 2 years.
Probably not - I may be wrong but power and what you can and can't put on
the same die are likely to mean that small RAM devices are here for a
while and in fact the CFO will be ordering the engineers to get it in
less RAM to save 20 cents a unit.
> And yes, I don't claim Moore's law will go on forever and I'm oversimplifying -
> maybe things are slowing down and it will only be 1.5 MB, but the point remains:
> the importance of your 20kb .text savings will become a 10-15k .text savings in
> just 2 years. In 8 years today's 1 MB system will be a 32 MB system if that trend
> holds up.
Power means it's more likely IMHO that todays 256K RAM system will in a
few years be either a 64K RAM system or have tons of persistent memory.
Alan
next prev parent reply other threads:[~2017-06-08 18:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 23:24 Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 1/8] cpuset/sched: cpuset makes sense for SMP only Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 2/8] sched: omit stop_sched_class when !SMP Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 3/8] futex: make PI support optional Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 4/8] sched/deadline: move dl related code out of sched/core.c Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 5/8] sched/rt: move rt " Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 6/8] sched/deadline: make it configurable Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 7/8] rtmutex: compatibility wrappers when no RT support is configured Nicolas Pitre
2017-06-06 23:24 ` [PATCH v2 8/8] sched/rt: make it configurable Nicolas Pitre
2017-06-07 16:00 ` [PATCH v2 0/8] scheduler tinification Ingo Molnar
2017-06-07 17:09 ` Nicolas Pitre
2017-06-07 18:49 ` Alan Cox
2017-06-07 21:15 ` Nicolas Pitre
2017-06-07 21:53 ` Alan Cox
2017-06-08 7:59 ` Ingo Molnar
2017-06-08 18:14 ` Alan Cox [this message]
2017-06-08 20:16 ` Nicolas Pitre
2017-06-11 9:23 ` Ingo Molnar
2017-06-11 15:26 ` Nicolas Pitre
2017-06-11 9:42 ` Ingo Molnar
2017-06-11 16:45 ` Nicolas Pitre
2017-06-13 7:12 ` Ingo Molnar
2017-06-13 12:29 ` Nicolas Pitre
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=20170608191429.2e454aa9@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®