From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Intel atom motherboard - success at last
Date: Wed, 5 Aug 2009 07:30:53 -0400 [thread overview]
Message-ID: <fde11bf1cc7209a09fe4401ae2c01b1b@quanstro.net> (raw)
In-Reply-To: <d57e1e86850e26a7f09a0c5741e8361c@hamnavoe.com>
> The dual-processor epia board was pretty snappy but it's no longer
> available.
>
> Many of the via processors have sha-1 in microcode, which could
> be useful for a venti server if someone got around to putting the
> support into libsec.
only if sha1 speed is a bottleneck. is it?
- erik
next prev parent reply other threads:[~2009-08-05 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 18:43 Steve Simon
2009-08-04 22:57 ` David Leimbach
2009-08-04 23:33 ` erik quanstrom
2009-08-05 0:32 ` Roman V Shaposhnik
2009-08-05 0:36 ` erik quanstrom
2009-08-05 9:21 ` Richard Miller
2009-08-05 9:28 ` Richard Miller
2009-08-05 11:30 ` erik quanstrom [this message]
2009-08-06 8:45 ` Nick LaForge
2009-08-07 2:09 ` Roman Shaposhnik
2009-08-07 2:17 ` Tharaneedharan Vilwanathan
2009-08-06 23:10 ` Fernan Bolando
2009-08-06 23:35 ` erik quanstrom
2009-08-07 3:49 ` erik quanstrom
2009-08-07 15:30 ` Fernan Bolando
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=fde11bf1cc7209a09fe4401ae2c01b1b@quanstro.net \
--to=quanstro@quanstro.net \
--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).