All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Schwartz <bruce.schwartz@gmail.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] 256 node limit
Date: Wed Jul  6 16:20:04 2005	[thread overview]
Message-ID: <11fa5cce05070614202aba490@mail.gmail.com> (raw)
In-Reply-To: <20050706190440.GN8215@ca-server1.us.oracle.com>

Thanks for all the great responses. I had only skimmed the ocfs2 code and 
hadn't looked at heartbeat, dlm, etc. so I had missed the various u8's. 
Certainly the scope of the problem is much clearer now and I'm glad to hear 
that there isn't anything particularly difficult about it (at least up to 
the point where the number of nodes would require kmalloc instead of 
allocating off the stack). There's just lots of mechanical changes get 
right.

Thanks again and I'll report back if I actually try this.

-Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20050706/f3252bc6/attachment.html

      reply	other threads:[~2005-07-06 16:20 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
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 [this message]

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=11fa5cce05070614202aba490@mail.gmail.com \
    --to=bruce.schwartz@gmail.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.