On Feb 1, 2008, at 10:02 AM, Walter B. Ligon III wrote:
Murali, Sam, thanks, that explains the macro naming!
I figured that the skip was for aligning on 64 bit, I'm still not
exactly sure where it is used. Do we actually encode a pointer when
we have an array?
Each element of the array
Hi Sam,
> Maybe part of the confusion that Walt&Co have is that the an array
> macro (3a_struct) always includes an extra uint32_t for the length of
> the array, but that field is not counted in the number used in the
> name of the macro. For example:
Yep.. I think that was the same confusion I
On Jan 30, 2008, at 2:07 PM, Sam Lang wrote:
On Jan 30, 2008, at 11:39 AM, Murali Vilayannur wrote:
Hi Walt,
In src/proto/pvfs2-req-proto.h when you define a new request you
create
a struct and then use a macro to create an encoding function for the
struct (endecode_fields_X_struct). Som
On Jan 30, 2008, at 11:39 AM, Murali Vilayannur wrote:
Hi Walt,
In src/proto/pvfs2-req-proto.h when you define a new request you
create
a struct and then use a macro to create an encoding function for the
struct (endecode_fields_X_struct). Sometimes, in the args to those
macros you insert a
Hi Walt,
> In src/proto/pvfs2-req-proto.h when you define a new request you create
> a struct and then use a macro to create an encoding function for the
> struct (endecode_fields_X_struct). Sometimes, in the args to those
> macros you insert a skip4,, which I gather is used to align something.
>
High,
I'm working with our new development team here and we are looking at how
to add requests to the server. A question came up wrt encoding that I
couldn't answer - I hear Pete is the expert, but anyone can pipe up.
In src/proto/pvfs2-req-proto.h when you define a new request you create
a
