From: Wim Coekaerts <wim.coekaerts@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] using ethernet instead of TCP
Date: Sat, 8 Apr 2006 21:13:38 -0700 [thread overview]
Message-ID: <20060409041337.GG21199@ca-server1.us.oracle.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77DCEBF59@trantor>
nope not yet :)
On Sun, Apr 09, 2006 at 01:56:32PM +1000, James Harper wrote:
> Has anyone considered having the option of using Ethernet instead of TCP
> for inter-node communications? Such a feature would be useful for me as
> I'd like to use the same Ethernet segment for inter-node communication
> as I run AoE over (much less chance of a split brain), but I don't
> currently run IP on that segment. Also, running ocfs2 as the root
> filesystem would be easier (I've asked on -users if this is a good idea,
> as discussion of that aspect probably isn't appropriate to -devel) as IP
> wouldn't need to be started before bringing the root filesystem online.
>
> Obviously it's going to limit the cluster to the one lan segment, and
> you get a lot of stuff 'for free' with TCP that would have to be written
> for ocfs2 to use Ethernet (but I don't know how much the inter-node
> stuff actually makes use of it), so it might be too much work for too
> little gain...
>
> Thanks
>
> James
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2006-04-09 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 3:56 [Ocfs2-devel] using ethernet instead of TCP James Harper
2006-04-09 4:13 ` Wim Coekaerts [this message]
2006-04-10 19:11 ` Zach Brown
2006-04-14 12:10 ` Michael Steinmann
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 2:12 James Harper
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=20060409041337.GG21199@ca-server1.us.oracle.com \
--to=wim.coekaerts@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.