9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: fernanbolando@mailc.net, 9fans@9fans.net
Subject: Re: [9fans] oh, no! (again)
Date: Thu, 13 Aug 2009 10:33:42 -0400	[thread overview]
Message-ID: <d0ae3afb9a53bbc202faaf6a38257771@quanstro.net> (raw)
In-Reply-To: <1d5d51400908130710i67f655f3rddd04d99160c9fe3@mail.gmail.com>

On Thu Aug 13 10:16:09 EDT 2009, fernanbolando@mailc.net wrote:
> >        quanstro/9load-e820     (to rebuild 9load)
>
> I am suppose to replace /sys/src/boot/pc with /sys/src/boot/pc-e820???

if you do reinstall, you will need to install from /sys/src/boot/pc-e820
not /sys/src/boot/pc. if you leave /sys/src/boot/pc there or not doesn't matter.

> There is no edev->maxtu in /sys/src/9/pc ether8169.c
> there is edev->maxmtu Mtu same thing???

i don't believe you've installed the version of 8169 in
my contrib.

> > also you may wish to enable support for the new sd stuff.
> >        quanstro/atazz          (send raw ata commands)
> >        quanstro/smart          (smart monitor)

that didn't come out right.  if you're using the new sd stuff, then
these command will work, and you might find them useful.
smart has a better chance of being useful than the rather esoteric
atazz.

> >
> > there are a few things in the kernel i've built that don't fit
> > in dist packages very well.
> >        PAT
> >        jumbo ethernet frames
> >        kernel cec server               (console-over-ethernet)
> >        /dev/cputemp
> >        /dev/nomp               (mptables when not enabled)
> >
>
>  not sure what to do here.

this was just fyi.  these will be differences between the prebuilt
kernel on the iso and one you can rebuild yourself.

i forgot some things like jumbo frames, too.  this is important
for good aoe performance.  i've gotten over 1GB/s of sustaned aoe
traffic on a lowly 1.6ghz xeon 5000 machine over a myricom
10gbe card.  when i get back to working on the myricom stuff,
i will post a link to the exact setup.

again, the iso is just kind of a bandaid.  the contrib packages
are, too.  it's all quite unsatisfactory.  sorry i havn't done a better job.
i'm up for suggestions.

- erik



  reply	other threads:[~2009-08-13 14:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 13:28 cej
2009-08-11 13:55 ` erik quanstrom
2009-08-11 14:17 ` erik quanstrom
2009-08-11 16:12   ` cej
2009-08-11 16:26     ` erik quanstrom
2009-08-11 17:57       ` erik quanstrom
2009-08-11 19:04         ` David Leimbach
2009-08-11 19:25           ` erik quanstrom
2009-08-11 20:51             ` Fernan Bolando
2009-08-11 21:17               ` erik quanstrom
     [not found]               ` <7ed7d1dd2bafb28e91ed462c526409e6@quanstro.net>
2009-08-12 12:12                 ` Fernan Bolando
2009-08-12 12:40                   ` erik quanstrom
     [not found]                   ` <5e44a853596c9d4a4a751c14d0878855@quanstro.net>
2009-08-12 14:06                     ` Fernan Bolando
2009-08-13 14:10         ` Fernan Bolando
2009-08-13 14:33           ` erik quanstrom [this message]
     [not found]           ` <855df96e3e51a2f75d1bce104eddda2f@quanstro.net>
2009-08-13 14:49             ` Fernan Bolando
2009-08-13 14:54               ` erik quanstrom

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=d0ae3afb9a53bbc202faaf6a38257771@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=fernanbolando@mailc.net \
    /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).