From: Isaac Huang <He.Huang@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] client side reply handling
Date: Tue, 15 Dec 2009 21:48:18 -0500 [thread overview]
Message-ID: <20091216024818.GA1196@sun.com> (raw)
In-Reply-To: <2b20c7140912151801m78871060pd20e5136c105b507@mail.gmail.com>
On Tue, Dec 15, 2009 at 07:01:33PM -0700, Peter Braam wrote:
> No - buffers can and probably should (because, for example, re-delivery
> may leaver buffer state undefined) be unlinked from the match list
> before passing the buffer up to any other layer. Portals/LNET
> certainly can do this.
Hi Peter, LNet does have a MD option to automatically unlink the
buffer once it's been exhausted. Duplicated delivery shouldn't cause any
problem because MD offset is increased locally (i.e. a dup would go
into a different offset), unless the MD has enabled peers to manage
offset remotely, which is now true for PTLRPC reply buffers (because
now early replies and real reply share a same reply buffer).
Isaac
next prev parent reply other threads:[~2009-12-16 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 15:05 [Lustre-devel] client side reply handling Peter Braam
2009-12-15 16:28 ` Yuriy Umanets
2009-12-16 2:01 ` Peter Braam
2009-12-16 2:48 ` Isaac Huang [this message]
2009-12-16 2:51 ` Isaac Huang
2009-12-16 2:55 ` Liang Zhen
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=20091216024818.GA1196@sun.com \
--to=he.huang@sun.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox