From: Richard Salz <rich.salz@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Bakul Shah <bakul@iitbombay.org>
Subject: Re: [TUHS] 386BSD released
Date: Fri, 16 Jul 2021 16:24:10 -0400 [thread overview]
Message-ID: <CAFH29trY2ZBcssDawauQWMEKzLc+7ZVeVOcXWc_50et7LcFtHw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2M7ytkKEwTeBvZySJtr2XLNiQjphhJ-66ZTuKfsviJHOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2627 bytes --]
Anyone remember the old mtXinu calendar with fake ads?I only remember one
page, "oh no Spot(?) spilled the mbufs, Dad's favorite cereal."
On Fri, Jul 16, 2021, 4:19 PM Clem Cole <clemc@ccc.com> wrote:
>
>
> On Fri, Jul 16, 2021 at 3:08 PM Kevin Bowling <kevin.bowling@kev009.com>
> wrote:
>
>> Yup was just going to say this is standard in the modern BSD network
>> drivers, looks like Clem says it's older.
>
> Absolutely -- I believe it was Rob's undergrad project at Brown that he
> brought to BBN.
>
> The first use, if I saw, was the 'portable IP/TCP' stack BBN did for
> HP/3000 and a couple of other systems. That code seems to have been lost.
> I have asked about it on the Internet history mailing list. I had a copy
> of it one time, but sadly I don't think I still do. IIRC The original
> PDP-11 IP implementation which ran on a couple of dedicated systems,
> whose names/function I frankly do not remember) was also based on a version
> of this code. I think it ran something like RT-11 or DOS-11 and then
> started the IP code -- basically RTR style today. Later it morphed into
> Rob's Vax BSD 4.1 specific stack, which we ran at UCB on a couple of the
> systems using 3M Xerox board. This latest until 4.1A and Joy's rewrite and
> I want to say we switched in Interlan 10M boards then. We have a couple of
> the 3Com boards, but because of the lack of buffering, they were a bear to
> use and stopped as soon as we got the Interlan one.
>
>
> Anyway, all of these IP/TCP stacks used Rob's mbuf code. Which was a
> blessing and a curse. By writing his own, he avoids huge
> changes/integration into the memory system, but it also helped to make BSD
> such a mess under the covers because there were so many private memory
> managers between the network, the I/O systems etc... As discussed
> previously on the TUHS list, the one thing Risner really did well had a
> uniform memory design. Later BSD's moved to Mach and tried to clean this
> up a little, but the network code was by then so screwed into Rob's mbuf
> scheme, it stayed around a long time. Werner -- what is the state of this
> these days in FreeBSD is it still there?
>
>
>
>
>> There are recent optimizations to help the CPU with prefetch, and some
>> ideas around vectors of mbufs. What's remarkable is the mbuf design
>> scales to
>> 200gbps in practice, it must feel great to design something like that so
>> long ago :)
>>
> Well, ask Rob :-) I've lost track of him since Stellar, and I think he I
> heard he left high tech but frankly don't know.
>
> Clem
> ᐧ
>
[-- Attachment #2: Type: text/html, Size: 4823 bytes --]
next prev parent reply other threads:[~2021-07-16 20:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 22:28 Dave Horsfall
2021-07-14 7:54 ` Michael Kjörling
2021-07-14 8:19 ` Angus Robinson
2021-07-14 8:32 ` Michael Kjörling
2021-07-14 9:07 ` Lars Brinkhoff
2021-07-14 14:09 ` Larry McVoy
2021-07-14 14:54 ` Warner Losh
2021-07-14 15:06 ` Richard Salz
2021-07-14 15:37 ` Steve Nickolas
2021-07-14 10:09 ` Tom Ivar Helbekkmo via TUHS
2021-07-14 10:39 ` arnold
2021-07-14 17:21 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-14 17:32 ` Richard Salz
2021-07-14 15:01 ` Clem Cole
2021-07-14 17:40 ` [TUHS] [COFF] " Theodore Y. Ts'o
2021-07-14 17:50 ` Larry McVoy
2021-07-14 18:28 ` Clem Cole
2021-07-14 11:49 ` [TUHS] " Andy Kosela
2021-07-14 15:48 ` Theodore Y. Ts'o
2021-07-16 1:35 ` Dave Horsfall
2021-07-16 2:33 ` risner
2021-07-16 4:25 ` Theodore Y. Ts'o
2021-07-16 5:51 ` Bakul Shah
2021-07-16 13:00 ` Theodore Y. Ts'o
2021-07-16 13:56 ` Larry McVoy
2021-07-16 14:40 ` Clem Cole
2021-07-16 15:44 ` Theodore Y. Ts'o
2021-07-16 16:11 ` Bakul Shah
2021-07-16 19:07 ` Kevin Bowling
2021-07-16 20:17 ` Clem Cole
2021-07-16 20:24 ` Richard Salz [this message]
2021-07-18 13:13 ` arnold
2021-07-18 13:23 ` Richard Salz
2021-07-18 13:43 ` [TUHS] MtXinu calendar (was Re: 386BSD released) Al Kossow
2021-07-18 13:51 ` Al Kossow
2021-07-18 16:44 ` Al Kossow
2021-07-18 17:38 ` John Cowan
2021-07-18 18:35 ` Bakul Shah
2021-07-19 3:06 ` Dan Stromberg
2021-07-18 19:00 ` arnold
2021-07-18 21:48 ` Deborah Scherrer
2021-07-18 20:06 ` Lyle Bickley
2021-07-14 21:37 ` [TUHS] 386BSD released Bakul Shah
2021-07-16 21:22 ` Dave Horsfall
2021-07-15 2:21 Douglas McIlroy
2021-07-15 2:41 ` Adam Thornton
2021-07-15 15:07 ` Clem Cole
2021-07-16 17:30 Nelson H. F. Beebe
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=CAFH29trY2ZBcssDawauQWMEKzLc+7ZVeVOcXWc_50et7LcFtHw@mail.gmail.com \
--to=rich.salz@gmail.com \
--cc=bakul@iitbombay.org \
--cc=clemc@ccc.com \
--cc=tuhs@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).