From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Query to understand the Lustre request/reply message
Date: Wed, 13 Oct 2010 19:28:45 -0500 [thread overview]
Message-ID: <20101014002844.GY1635@oracle.com> (raw)
In-Reply-To: <AANLkTinJOer5Uid0X3pG3nK_RYkxzsoYsmtLPA20Lsj4@mail.gmail.com>
On Wed, Oct 13, 2010 at 07:51:37PM -0400, Vilobh Meshram wrote:
> 1) Is it possible that without writing a new RPC in Lustre 1.8.1.1 I can
> append some string such as "Hello" to the exsisting message sent by the
> Client (with the buffer size set at client side by the count,size fields).I
> tried modifying the "size" of the request for one of the RPC in-built in
> Lustre
Yes, it's possible to add buffers to requests. It's not possible to add
buffers to _replies_ to existing RPCs unless you know the client expects
those additional buffers -- existing clients expect a given maxsize for
each reply, and if your reply is bigger then it will get dropped.
> __u32 size[2] = { [MSG_PTLRPC_BODY_OFF] = sizeof(struct
> ptlrpc_body),
> [DLM_LOCKREQ_OFF] = sizeof(struct
> ldlm_request) };
>
> ---->>
> __u32 size[3] = { [MSG_PTLRPC_BODY_OFF] = sizeof(struct ptlrpc_body),
> [DLM_LOCKREQ_OFF] = sizeof(struct
> ldlm_request) ,
> //how to add "char *str=Hello" ofcourse we
> will have sizeof(str) but how to choose the MACRO like DLM_LOCKREQ_OFF bcz
> for a specific kind of RPC there are limited number of such MACROS
> };
Add a buffer. Don't change the size of an existing buffer.
> The thing I want to know is how can I send a buffer from the client side by
> modifying the static structure "size" mentioned above.What all main places
> do I need to consider to make this work.
Add an element to the size[] array, then set it to the correct size when
you know the length of the string. Look at the SET_INFO RPCs.
> If the above step i.e appending a buffer in the "size" array is not possible
> then I can move to write a new RPC.
The size[] array is just a convenient place to store the sizes of the
individual buffers while you construct them.
Nico
--
next prev parent reply other threads:[~2010-10-14 0:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 17:55 [Lustre-devel] Query to understand the Lustre request/reply message Vilobh Meshram
2010-10-12 18:21 ` Alexey Lyashkov
2010-10-12 22:17 ` Vilobh Meshram
2010-10-13 3:46 ` Alexey Lyashkov
2010-10-13 4:06 ` Vilobh Meshram
2010-10-13 4:20 ` Alexey Lyashkov
2010-10-13 4:35 ` Vilobh Meshram
2010-10-13 4:41 ` Alexey Lyashkov
2010-10-13 5:42 ` Nicolas Williams
2010-10-13 5:54 ` Alexey Lyashkov
2010-10-13 7:15 ` Nicolas Williams
2010-10-13 7:32 ` Alexey Lyashkov
2010-10-13 6:07 ` Vilobh Meshram
2010-10-13 7:17 ` Nicolas Williams
2010-10-13 6:25 ` Alexey Lyashkov
2010-10-13 7:12 ` Nicolas Williams
2010-10-13 7:27 ` Alexey Lyashkov
2010-10-13 7:43 ` Nicolas Williams
2010-10-13 7:51 ` Alexey Lyashkov
2010-10-13 23:51 ` Vilobh Meshram
2010-10-14 0:28 ` Nicolas Williams [this message]
2010-10-14 1:41 ` Vilobh Meshram
2010-10-14 3:38 ` Alexey Lyashkov
2010-10-14 5:18 ` Nicolas Williams
2010-10-14 5:46 ` Alexey Lyashkov
2010-10-14 14:31 ` Andreas Dilger
2010-10-14 14:40 ` Alexey Lyashkov
2010-10-14 15:04 ` Vilobh Meshram
2010-10-14 15:10 ` Alexey Lyashkov
2010-10-14 15:29 ` Vilobh Meshram
2010-10-14 15:45 ` Alexey Lyashkov
2010-10-14 16:25 ` Vilobh Meshram
2010-10-15 0:58 ` Vilobh Meshram
2010-10-15 7:39 ` Alexey Lyashkov
2010-10-15 16:25 ` Vilobh Meshram
2010-10-15 17:22 ` Alexey Lyashkov
2010-10-14 8:44 ` Alexey Lyashkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101014002844.GY1635@oracle.com \
--to=nicolas.williams@oracle.com \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.