From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] 256 node limit
Date: Tue Jul 5 18:23:47 2005 [thread overview]
Message-ID: <42CB1689.8040800@oracle.com> (raw)
In-Reply-To: <11fa5cce05070116517b7339b5@mail.gmail.com>
It's actually 255. Yes, that doc needs to be updated.
No, the algorithms did not play much role in setting this limit.
Guess, can say the limit is part arbitrary, part practical.
(That extra byte adds up pretty quickly.)
Bruce Schwartz wrote:
> Hi all --
>
> In the "what's new in OCFS2" document at
> http://oss.oracle.com/projects/ocfs2/dist/documentation/ocfs2-whats-new.txt
> it says that the 256 node limit is a software limit and could be
> lifted. Why is that limit there? Are there some algorithms that
> don't scale nicely with larger number of nodes? I'm guessing that
> there is more to it than saving a byte of RAM in a few data structures.
>
> Thanks,
> Bruce
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Ocfs2-devel mailing list
>Ocfs2-devel@oss.oracle.com
>http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>
>
next prev parent reply other threads:[~2005-07-05 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200507011649.j61GnMlY022352@oss.oracle.com>
2005-07-01 12:05 ` [Ocfs2-devel] Re: [Ocfs2-commits] zab commits r2451 - trunk/fs/ocfs2/cluster Lars Marowsky-Bree
2005-07-01 13:20 ` Zach Brown
2005-07-01 18:51 ` [Ocfs2-devel] 256 node limit Bruce Schwartz
2005-07-05 18:23 ` Sunil Mushran [this message]
2005-07-06 12:38 ` Bruce Schwartz
2005-07-06 13:04 ` Wim Coekaerts
2005-07-06 13:51 ` Kurt Hackel
2005-07-06 13:57 ` Mark Fasheh
2005-07-06 14:04 ` Mark Fasheh
2005-07-06 16:20 ` Bruce Schwartz
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=42CB1689.8040800@oracle.com \
--to=sunil.mushran@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.