+1 Also, if your xlator is useful to the greater community, please consider releasing it on the Gluster forge - forge.gluster.org On Dec 16, 2013 6:03 AM, "Pranith Kumar Karampuri" <pkara...@redhat.com> wrote:
> hi Mingfan Lu, > xlators are not supposed to know which part of the stack they belong > to. If you think the functionality needs to be different when it is in > server vs client side. Would writing two different xlators one for client > side and the other for server side make sense? May be knowing a bit more > about what you want to implement may give a better understanding for us to > suggest better. > > Pranith. > ----- Original Message ----- > > From: "Mingfan Lu" <mingfan...@gmail.com> > > To: gluster-devel@nongnu.org > > Sent: Monday, December 16, 2013 2:55:24 PM > > Subject: [Gluster-devel] how to distinguish whether the current xlator > is used in the client or the server? > > > > When I write a xlator for glusterfs, the xlator could be used for client > and > > server. but when being used in server and client, the behavior of the > xlator > > could be some-what differrent. How could I know whether the xlator is > used > > in glusterfs or glusterfsd when I developing the xlator? then I could > tune > > the code path for client and server. > > > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@nongnu.org > > https://lists.nongnu.org/mailman/listinfo/gluster-devel > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/gluster-devel >
_______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel
