9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Wolfgang Kunz" <woku@hush.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Hardware for Plan9
Date: Mon, 11 Jan 2010 09:24:08 +0100	[thread overview]
Message-ID: <20100111082408.3F3BE2803F@smtp.hushmail.com> (raw)

Hello,

>this isn't a complete list of supported ahci or marvell
>parts.  i don't know about jmicron support.  i tried
>to add it without having any hardware to test.  i have
>always chosen other hardware over jmicron.  it seems
>to benchmark poorly and be unnecessarly incompatable.
>
>i have not done systematic benchmarking of the
>various parts.  however ..
>
>1.  unless one needs more ports than the motherboard
>offers, i would stick with on-board ports.

That makes sense for me. Perhaps I could save money and
use the onboard network chip too (most RELTEK)? Then I
could invest more money in the board and the CPU.

>2.  note that the marvell 88sx card is pci-x but will
>function properly in a pci slot.  the marvell 88se64*
>parts are a pci-e option.

I saw that this cards are really expensive. As you said
the onboard controller are a better choise.

>3.  if you set up a venti+fossil fileserver, you will have
>a quite seeky load and the performance of the controller
>should not be a big factor.  but the performance of the
>disks will be.

After reading many mails here I plan to run a fossil only
fileserver. So far I understand the "Ken" dedicated fileserver
has gone.

So disks >= 7200 u/min are ok?

>> For network cards the intel gbe cards seems to be the best?
>
>yes.  the 82563 and 8257[12456] are particularly good.

I could get a 82574L (PCIe) (Desktop pro CT - EXPI9301CT) for 30$.
Would this be a good buy?

Regards,

Wolfgang




             reply	other threads:[~2010-01-11  8:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11  8:24 Wolfgang Kunz [this message]
2010-01-11 13:39 ` erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2010-01-13  6:46 Wolfgang Kunz
2010-01-11 19:47 Wolfgang Kunz
2010-01-11 20:05 ` erik quanstrom
2010-01-11 17:52 Wolfgang Kunz
2010-01-11 18:00 ` Frederik Caulier
2010-01-11 20:31   ` Akshat Kumar
2010-01-13 12:49     ` matt
2010-01-13 13:28       ` erik quanstrom
2010-01-13 18:16       ` Akshat Kumar
2010-01-11 18:14 ` erik quanstrom
2010-01-11  8:33 Wolfgang Kunz
2010-01-11 13:41 ` erik quanstrom
2010-01-11 19:50 ` Federico G. Benavento
2010-01-11  8:27 Wolfgang Kunz
2010-01-11 13:01 ` Steve Simon
2010-01-11 14:07   ` Venkatesh Srinivas
2010-01-11 15:22     ` erik quanstrom
2010-01-11 16:54       ` Venkatesh Srinivas
2010-01-11 17:24         ` erik quanstrom
2010-01-11 17:29           ` Venkatesh Srinivas
2010-01-11 13:51 ` erik quanstrom
2010-01-11 16:43   ` Steve Simon
2010-01-11 17:26     ` erik quanstrom
2010-01-10 13:39 Wolfgang Kunz
2010-01-10 14:06 ` Steve Simon
2010-01-10 15:59 ` erik quanstrom
2010-01-10 16:14   ` Federico G. Benavento
2004-02-16 15:11 [9fans] Hardware for plan9 Ryan
2004-02-16 15:39 ` matt
2004-02-16 15:57 ` David Cantrell
2004-02-16 15:59 ` Jim Choate

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=20100111082408.3F3BE2803F@smtp.hushmail.com \
    --to=woku@hush.com \
    --cc=9fans@9fans.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).