From: Tobias Groschup <groschup@stud.uni-heidelberg.de>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] LND Development
Date: Wed, 07 Aug 2013 12:48:04 +0200 [thread overview]
Message-ID: <520225E4.1070000@stud.uni-heidelberg.de> (raw)
Hi all,
I am a student of applied Computer Science at the University of
Heidelberg and I am currently working on my master thesis about
distributed file systems on networks capable of Remote Direct Memory Access.
I work at the Computer Architecture Group, which develops a High Speed
Interconnect for High Performance Computing called Extoll. I have
experience in developing Linux kernel modules, as I work on Extolls
driver stack, including a kernel level API to access the Extoll device.
Our aim is to implement a LND which supports Extoll.
So I started to build the current lustre-master and the patched kernel
from scratch, which worked very well, thanks to the good documentation
online.
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.
Also, the Doxygen generated from the LNet source files was not very helpful.
So my question is: where do I start to implement a LND?
And: how can I test a LND without recompiling the whole Lustre RPM?
Thanks
Tobias Groschup
next reply other threads:[~2013-08-07 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 10:48 Tobias Groschup [this message]
2013-08-07 20:39 ` [Lustre-devel] LND Development Isaac Huang
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=520225E4.1070000@stud.uni-heidelberg.de \
--to=groschup@stud.uni-heidelberg.de \
--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.