From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] ARM hardware and SATA
Date: Thu, 12 Dec 2019 15:14:18 +0000 [thread overview]
Message-ID: <CAFSF3XN387Y+quvcOKgea68s5bd7hoA0ghzc60t_NJXjs0KLvw@mail.gmail.com> (raw)
In-Reply-To: <644326F9-F36C-407A-9436-7F2F58909810@pobox.com>
generally, i would like better hardware, too. i'm especially curious
about chipsets that include QSFP or even QSFP+ with lowest possible
total power consumption in idle. not much random computation power
needed, but i want all the benefits of full throughput at 10gbit or
40gbit, speeding up sequential file transfers like backups. i.e. at
big block size.
next prev parent reply other threads:[~2019-12-12 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 6:31 Lucio De Re
2019-12-12 8:30 ` [9fans] " Dan Cross
2019-12-12 8:54 ` Bakul Shah
2019-12-12 12:15 ` Juan Cuzmar
2019-12-12 12:43 ` hiro
2019-12-12 13:02 ` Juan Cuzmar
2019-12-12 13:14 ` Matthew Singletary
2019-12-12 14:10 ` Dan Cross
2019-12-12 14:14 ` Juan Cuzmar
2019-12-12 13:20 ` David Arnold
2019-12-12 15:14 ` hiro [this message]
2019-12-12 15:24 ` hiro
2019-12-12 15:31 ` hiro
2019-12-13 7:08 ` Dan Cross
2019-12-13 10:28 ` hiro
2019-12-14 6:13 ` David Arnold
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=CAFSF3XN387Y+quvcOKgea68s5bd7hoA0ghzc60t_NJXjs0KLvw@mail.gmail.com \
--to=23hiro@gmail.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).