On 09/27/2013 09:34 AM, Benny Halevy wrote: >> I thought that we said that exofs server is going in first. What happened? > > exofs requires much more functionality. > To help review the code we need to go through this milestone in any case. > That is not true. Look at the way I staged the pnfsd-exofs patches. after the LO_GET LO_COMMIT and LO_RETURN patches you have a full functioning git cloning exofs. (BTW exofs does not need DEVICELIST) So OK your patches do not have LO_COMMIT but this code path is trivial and what is that contraption of returning "no-layout" for writes and then not having the LO_COMMIT support. This is plain hacky and not in accord to the pNFS philosophy of things. And We can farther split my original set to do read-only with out LO_COMMIT and add a simple LO_COMMIT stage with enable of write LAYOUTs, easily. Which is what you have with much less code. The recall comes in at a different patch that can be staged later and is effectively not needed for normal operations. Actually the all code including the exofs patches first stage is smaller and simpler then the DLM contraption. And it only touches exofs code which does not involve other sensitive subsystems. I have a deja vu about this. Why won't you talk to me before working on such DLM crap that is not at all pnfs, but a hack that demonstrates nothing? Please do the right thing, since you are already putting all this effort. And I can help as well with the pnfsd-exofs patches part. BTW: Thank you for doing this, it is about time someone should put some mainline love to the pNFS server Thanks Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
