lkml.org 
[lkml]   [2006]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 14/16] GFS2: The DLM interface module
Hi David,


>> >+int gdlm_get_lock(lm_lockspace_t *lockspace, struct lm_lockname *name,
>> >+ lm_lock_t **lockp)
>>
>> [lm_lock_t is]
>> currently typedef'ed to void [...]. (One _could_
>> get rid of it, but better not while it is called lm_lock_t. Leave as-is
>> for now.)
>
>I'm wondering what you might suggest instead of using the lm_lockspace_t,
>lm_lock_t, lm_fsdata_t typedefs. These are opaque objects passed between
>gfs and the lock modules. Could you give an example or point to some code
>that shows what you're thinking?

What I was thinking about:
int gdlm_get_lock(void *lockspace, struct lm_lockname *name, void **lockp)


Jan Engelhardt
--
-
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/

\
 
 \ /
  Last update: 2006-09-07 18:41    [W:0.034 / U:5.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site