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 02:12:02 -0500 [thread overview]
Message-ID: <20101013071201.GD1635@oracle.com> (raw)
In-Reply-To: <B315579D-2A4F-482F-B02E-679441D4CA66@clusterstor.com>
On Wed, Oct 13, 2010 at 09:25:00AM +0300, Alexey Lyashkov wrote:
>
> On Oct 13, 2010, at 08:42, Nicolas Williams wrote:
> >
> >
> > - add handlers for the new RPC to mdt_handler.c (for the MDS) or
> > ost_handler.c (for the OST), and so on
> >
> > The handlers are responsible for knowing which buffers contain what,
> > and for swabbing them. You have to make sure that you don't swab a
> > buffer more than once.
> >
> BTW.
> That not enough.
> Some of operations wants to have own recostructors for replay/resend.
I glossed over replay/resend, mostly because I know little about them,
but also because they are completely orthogonal to the message format
details. If you want to add an RPC then the first step should be to get
the RPC format designed and surrounding code up and running, then you
can take care of replay/resend.
> Some of operations want to have a return lock - as example MDS_GETATTR
> and MDS_REINT commands.
That too is orthogonal to the message formats. The message format has
to have a buffer (field) declared to carry lock (or capability, or
whatever) bits, and some function has to be invoked to populate the
buffer in the reply.
Nico
--
next prev parent reply other threads:[~2010-10-13 7:12 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 [this message]
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
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=20101013071201.GD1635@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.