Hi Ankur,
Just to clarify, have you added a new request type called "ecreate" or
is that a typo and you have just added a field to the existing "create"
struct?
This makes a difference in the extent of the changes that you will need
to make. If you are modifying an existing struct then the bulk of the
work is to just adjust the encoding macro in pvfs2-proto.h to capture
the new field properly. It should then get propagated to the server and
show up in its s_op->req->u.create struct in the state machine.
If you are adding a completely new request struct, that typically
implies creating new state machines on both the client and server side
that correspond to it (we may have a document on this that I can point
you to, its a bit more involved).
Sorry about the slow reply, but I think we can help you sort it out if
you are still working on this issue.
-Phil
Robert Latham wrote:
On Thu, Oct 02, 2008 at 06:46:42PM -0400, Pai, Ankur G wrote:
Hey,
Here is what I want to do. I want to send additional parameters
from my PVFS client to the server. I modified the client side
struct such that I now have an additional parameter
sm_p->req.u.ecreate.ACCESS_CTRL. I now need to transport it to
the server side. Could you direct me to the file that actually
assigns the client side parameters to the server ones? As in
where exactly does the server parameter s_op get populated?
I'm directing this to the pvfs2-developers mailing list.
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
