From: Warner Losh <imp@bsdimp.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] Unix Kernel Size
Date: Fri, 29 Jun 2018 18:57:53 -0600 [thread overview]
Message-ID: <CANCZdfp5xy8+Z3gpZ4+OacM_WLqBwdz_hajufKGvi-MFS4jWXw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Greetings,
I'd like to thank everybody that sent me data for my unix kernel size
stuff. There's two artifacts I've crated. One I think I've shared before,
which is my spreadsheet:
https://docs.google.com/spreadsheets/d/13C77pmJFw4ZBmGJuNarBUvWBxBKWXG-jtvARxJDHiXs/edit?usp=sharing
The second are some simplified graphs and the first half of my BSDcan talk:
http://www.bsdcan.org/2018/schedule/events/934.en.html
The video should be available soon for my talk as well, but it's not up
yet. If there's interest, I'll post an update when it is.
Warner
[-- Attachment #2: Type: text/html, Size: 941 bytes --]
next reply other threads:[~2018-06-30 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 0:57 Warner Losh [this message]
2018-06-30 19:11 ` Andy Kosela
2018-06-30 19:31 ` Warner Losh
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=CANCZdfp5xy8+Z3gpZ4+OacM_WLqBwdz_hajufKGvi-MFS4jWXw@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=tuhs@minnie.tuhs.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).