public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: teigland@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/dlm/lib libdlm.c libdlm.h
Date: Fri, 18 May 2007 16:35:00 -0000	[thread overview]
Message-ID: <20070518163516.29219.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland@sourceware.org	2007-05-18 16:35:16

Modified files:
	dlm/lib        : libdlm.c libdlm.h 

Log message:
	Make new features available based on recent dlm kernel patches.
	
	The kernel patches change the user/kernel device interface used by libdlm.
	(You'll need the new dlm_device.h kernel header installed on your system
	to build the lib.) libdlm is backward compatible with the old kernel
	interface, but some of the new features will return errors on old kernels.
	
	New API's provided by libdlm:
	- dlm_new_lockspace() is just like dlm_create_lockspace() but has a flags
	arg so flags can be passed when creating/joining a lockspace.
	- DLM_LSFL_NODIR and DLM_LSFL_TIMEWARN are new flags that can be used with
	dlm_new_lockspace().
	- dlm_ls_purge() is new and can be used to purge orphan locks.
	- all DLM_LKF flags can now be used with dlm_lock* routines (flags above
	16 bits couldn't be used before)
	- new DLM_LKF_TIMEOUT flag to enable lock timeouts
	- dlm_ls_lockx() is new and adds "xid" and "timeout" args
	
	All previous API's are still available, and programs compiled against
	previous versions of libdlm should still work.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/dlm/lib/libdlm.c.diff?cvsroot=cluster&r1=1.33&r2=1.34
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/dlm/lib/libdlm.h.diff?cvsroot=cluster&r1=1.13&r2=1.14


             reply	other threads:[~2007-05-18 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 16:35 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-05 16:35 teigland
2007-05-30 18:18 teigland
2005-03-14 14:15 pcaulfield

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=20070518163516.29219.qmail@sourceware.org \
    --to=teigland@sourceware.org \
    --cc=cluster-cvs@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).