Messages in this thread | | | Date | Thu, 28 Apr 2005 18:42:21 +0200 | From | Lars Marowsky-Bree <> | Subject | Re: [PATCH 0/7] dlm: overview |
| |
On 2005-04-29T00:25:52, David Teigland <teigland@redhat.com> wrote:
> On Wed, Apr 27, 2005 at 03:56:35PM +0200, Lars Marowsky-Bree wrote: > > > Questions which need to be settled, or which the API at least needs to > > export so we know what is expected from us: > > Here's what the dlm takes from userspace: > > - Each lockspace takes a list of nodeid's that are the current members > of that lockspace. Nodeid's are int's. For lockspace "alpha", it looks > like this: > echo "1 2 3 4" > /sys/kernel/dlm/alpha/members > > - The dlm comms code needs to map these nodeid's to real IP addresses. > A simple ioctl on a dlm char device passes in nodeid/sockaddr pairs. > e.g. dlm_tool set_node 1 10.0.0.1 > to tell the dlm that nodeid 1 has IP address 10.0.0.1 > > - To suspend the lockspace you'd do (and similar for resuming): > echo 1 > /sys/kernel/dlm/alpha/stop
Ohhh. _NEAT!_ Simple. Me like simple. This will work just perfectly well with our current approach (well, with some minor adjustments on our side for the mapping table).
I assume that we're allowed to update the nodeid/sockaddr mapping while suspended too? ie, if we were to reassign the nodeid to some other node...?
We can drive this almost directly and completely with a simple plugin.
> In other words, these aren't external API's; they're internal interfaces > within systems that happen to be split between the kernel and user-space.
Okay, understood. So the boundary is within user-space.
Sincerely, Lars Marowsky-Brée <lmb@suse.de>
-- High Availability & Clustering SUSE Labs, Research and Development SUSE LINUX Products GmbH - A Novell Business
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |