All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] lvb length issue [was Re: [ocfs2-tools-devel] question of ocfs2_controld (Jun 27)]
Date: Tue, 7 Jul 2009 11:01:13 -0500	[thread overview]
Message-ID: <20090707160113.GA9140@redhat.com> (raw)
In-Reply-To: <4A51ED7F.2040105@suse.de>

On Mon, Jul 06, 2009 at 08:26:39PM +0800, Coly Li wrote:
> DLM_USER_LVB_LEN is defined to 32.

> DLM_LVB_LEN is 64.

Yes, the kernel dlm api allows a variable lvb size, but the user dlm api fixes
it at 32.

Do you need to actually use a 64 byte lvb from userspace?  Or do you just need
to create the locksapce with a 64 byte lvb?  We could add a flag to work
around the later fairly easily.  Changing the dlm user/kernel interface to
copy variable size lvb's would take some significant work.

Dave

  reply	other threads:[~2009-07-07 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A451AB5.9070908@suse.de>
     [not found] ` <20090626193436.GC4478@mail.oracle.com>
     [not found]   ` <4A45257C.6040704@suse.de>
     [not found]     ` <20090629080023.GB8373@mail.oracle.com>
2009-07-06 12:26       ` [Ocfs2-devel] lvb length issue [was Re: [ocfs2-tools-devel] question of ocfs2_controld (Jun 27)] Coly Li
2009-07-07 16:01         ` David Teigland [this message]
2009-07-07 17:06           ` Coly Li
2009-07-07 17:24           ` Sunil Mushran
2009-07-07 18:35             ` Coly Li
2009-07-07 17:47           ` Joel Becker
2009-07-08 14:15             ` David Teigland
2009-07-09 18:53               ` David Teigland
2009-07-09 20:55                 ` Joel Becker
2009-07-09 21:55                   ` David Teigland
2009-07-09 22:28                     ` Joel Becker
2009-07-31 11:59                 ` Coly Li
2009-07-31 16:21                   ` David Teigland
2009-07-31 16:49                     ` Coly Li

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=20090707160113.GA9140@redhat.com \
    --to=teigland@redhat.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.