From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: single, comprehensive kernel data types document?
Date: Fri, 22 Apr 2016 12:13:37 +0900 [thread overview]
Message-ID: <20160422031337.GA20313@kroah.com> (raw)
In-Reply-To: <7422.1461294152@turing-police.cc.vt.edu>
On Thu, Apr 21, 2016 at 11:02:32PM -0400, Valdis.Kletnieks at vt.edu wrote:
> On Fri, 22 Apr 2016 11:37:13 +0900, Greg KH said:
>
> > As Josh says, this is fine, you just "burn" 4 bytes,
>
> Are there stil any platforms left where that matters? Sure, when I started
> coding, an HP2114 had all of 8K of RAM, so wasting 4 bytes mattered. But I
> don't know of anything that will boot Linux and is still so storaged
> constrained that we care. Heck, even my fairly old wireless router has 128M
> of RAM on it - and even THERE the 8M of flash is a bigger constraint :)
People cram Linux into machines with only 2M of ram, there are tons of
chips out there that are new and shipping in devices with less than 1M
of ram that would be great to have Linux running in them, but can't at
the moment.
So yes, in some systems it does matter, in others, it doesn't but that's
the beauty of Linux, it runs almost everywhere :)
thanks,
greg k-h
prev parent reply other threads:[~2016-04-22 3:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 12:04 single, comprehensive kernel data types document? Robert P. J. Day
2016-04-15 12:27 ` Greg KH
2016-04-15 12:37 ` John Chludzinski
2016-04-15 13:08 ` Silvan Jegen
2016-04-15 13:09 ` Daniel.
2016-04-15 13:55 ` Greg KH
2016-04-15 16:28 ` Daniel.
2016-04-15 13:53 ` Greg KH
2016-04-15 15:59 ` Nicholas Mc Guire
2016-04-15 16:18 ` Greg KH
2016-04-15 17:07 ` Valdis.Kletnieks at vt.edu
2016-04-15 20:15 ` Greg KH
2016-04-20 20:37 ` Rob Groner
2016-04-21 2:51 ` Greg KH
2016-04-21 12:51 ` Rob Groner
2016-04-21 19:34 ` Josh Cartwright
2016-04-22 2:37 ` Greg KH
2016-04-22 3:02 ` Valdis.Kletnieks at vt.edu
2016-04-22 3:13 ` Greg KH [this message]
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=20160422031337.GA20313@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).