Re: [Gluster-devel] how to distinguish whether the current xlator is used in the client or the server?

[Vijay Bellur]

On 12/16/2013 04:20 PM, Pranith Kumar Karampuri 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?

You can also consider having optional behavior and enable the 
appropriate option in the client/server volume files for the xlator to 
behave differently. For e.g. the compression translator is loaded in 
both client and server stacks, but it performs 
compression/de-compression for the appropriate fops by looking at option 
'mode'.

-Vijay


> Pranith.
> ----- Original Message -----
> > From: "Mingfan Lu" <address@hidden>
> > To: address@hidden
> > 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
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/gluster-devel
>
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/gluster-devel