From: Jeff Garzik <jgarzik@pobox.com>
To: Dan Stromberg <strombrg@dcs.nac.uci.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AOE and large filesystems?
Date: Tue, 05 Apr 2005 19:07:46 -0400 [thread overview]
Message-ID: <42531A42.90508@pobox.com> (raw)
In-Reply-To: <pan.2005.04.05.20.44.39.37209@dcs.nac.uci.edu>
Dan Stromberg wrote:
> Some questions for the list:
>
> 1) Is anyone on the list using AOE in production?
>
> 2) Is anyone on the list using AOE in combination with md and/or LVM2?
>
> 3) Is anyone on the list using AOE on a 64 bit platform?
While I think AoE is "neat", IMO you really want to use something based
on TCP, even on a LAN...
Your CPU usage w/ zerocopy offload could potentially be lowered w/ TCP,
in addition to the built-in reliability.
As a tangent, I'd also like to see iSCSI over SCTP.
Jeff
next prev parent reply other threads:[~2005-04-05 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 20:44 AOE and large filesystems? Dan Stromberg
2005-04-05 23:07 ` Jeff Garzik [this message]
2005-04-06 7:03 ` bert hubert
2005-04-06 16:44 ` Dmitry Yusupov
2005-04-09 10:06 ` Pavel Machek
2005-04-12 21:37 ` Ed L Cashin
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=42531A42.90508@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=strombrg@dcs.nac.uci.edu \
/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