Regarding your comments I do have a test implementation that takes care of
storing files_struct for local locks so this is not a problem.
(By the way, the use of that field to store that seems very bad idea imho)
Regarding IPv4 not being the only protocol, I would say yes that is a
problem and in fact I the one solution to this would be to enlarge
fl_owner field, but thats a lot of work.
In any case my main problem is to find a unique node identifier that is not
bound to the underlying protocol you are using without requiring
clustering between the nodes that are participating as part of nas head,
suggestions on how to create a clean portable solution are welcome.
Juan
|---------+---------------------------->
| | Matthew Wilcox |
| | <willy@debian.org|
| | > |
| | Sent by: |
| | <willy@www.linux.|
| | org.uk> |
| | |
| | |
| | 10/31/02 01:08 PM|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------|
| |
| To: Juan Gomez/Almaden/IBM@IBMUS |
| cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org |
| Subject: Re: Proposal for new lock ownership scheme to support NFS over distributed filesystems |
| |
| |
>------------------------------------------------------------------------------------------------------------------|
Hey, how about cc'ing either me or linux-fsdevel when discussing file
locking in the future as described in MAINTAINERS?
Your idea doesn't work because we need fl_owner to be the files_struct
for local locks. It also doesn't work because IPv4 is not the only
protocol which NFS runs over.
-- Revolutions do not require corporate support.
- 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/