From: Isaac Huang <he.huang@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] LND Development
Date: Wed, 7 Aug 2013 14:39:14 -0600 [thread overview]
Message-ID: <20130807203914.GA1099@intel.com> (raw)
In-Reply-To: <520225E4.1070000@stud.uni-heidelberg.de>
On Wed, Aug 07, 2013 at 12:48:04PM +0200, Tobias Groschup wrote:
> ......
> After consulting the Lustre Manual, some guides and papers including
> "The Lustre Storage Architecture" and "Understanding Lustre Filesystem
> Internals" I did not find an comprehensive overview for the API a LND
> has to implement. Although the function names are easy to find, its not
> clear what the expected behaviour of the function is, or with which
> ranges of input data they have to deal.
There's no document on the LND API as far as I know.
> Also, the Doxygen generated from the LNet source files was not very helpful.
That documents the external LNet API, not the LND API.
> So my question is: where do I start to implement a LND?
I'd suggest to read lnet/lnet/lo.c to get a basic understanding of the
LND API. That's the implementation of a simple loopback LND, similar
to the Linux lo if device.
If you're not already familiar with the LNet API, it'd be helpful to
understand its semantics, which is well documented by the LNet Doxygen
comments.
It's a difficult task to build a new LND. So far we have two 3rd party
LNDs contributed to Lustre. If you search the list archives for mxlnd
or gnilnd, you'd find some previous discussions on the LND API.
> And: how can I test a LND without recompiling the whole Lustre RPM?
You can test it with the LNet selftest tool. You'd only need to
compile and replace the LND.ko to test it.
- Isaac
next prev parent reply other threads:[~2013-08-07 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 10:48 [Lustre-devel] LND Development Tobias Groschup
2013-08-07 20:39 ` Isaac Huang [this message]
2013-08-14 12:20 ` Tobias Groschup
2013-08-14 23:13 ` Isaac Huang
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=20130807203914.GA1099@intel.com \
--to=he.huang@intel.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.