From: James Simmons <jsimmons@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>,
James Simmons <jsimmons@infradead.org>
Subject: [PATCH 0/4] Support lustre routers with stand alone LNet stack
Date: Tue, 8 Mar 2016 17:35:25 -0500 [thread overview]
Message-ID: <1457476529-27708-1-git-send-email-jsimmons@infradead.org> (raw)
Often lustre file systems will employ LNet routers in their
set ups. Those routers tend to be very light weight so we want
to avoid installing additional software that will burden the
system. Installing the entire lustre client can be pretty heavy
so we want to give the ability to only enable the LNet stack for
the routers which is all that is needed anyways. This patch series
allows that option for users of the upstream client.
James Simmons (4):
staging: lustre: move libcfs to lnet layer
staging: lustre: fixup kernel Kconfig option LNET_MAX_PAYLOAD
staging: lustre: add help section of Kconfig config LNET
staging: lustre: make lustre dependent on LNet
drivers/staging/Makefile | 2 +-
drivers/staging/lustre/Kconfig | 4 ++--
drivers/staging/lustre/lnet/Kconfig | 14 ++++++++++----
drivers/staging/lustre/lnet/Makefile | 2 +-
.../lustre/{lustre => lnet}/libcfs/Makefile | 2 +-
.../staging/lustre/{lustre => lnet}/libcfs/debug.c | 0
.../staging/lustre/{lustre => lnet}/libcfs/fail.c | 0
.../staging/lustre/{lustre => lnet}/libcfs/hash.c | 0
.../lustre/{lustre => lnet}/libcfs/libcfs_cpu.c | 0
.../lustre/{lustre => lnet}/libcfs/libcfs_lock.c | 0
.../lustre/{lustre => lnet}/libcfs/libcfs_mem.c | 0
.../lustre/{lustre => lnet}/libcfs/libcfs_string.c | 0
.../{lustre => lnet}/libcfs/linux/linux-cpu.c | 0
.../libcfs/linux/linux-crypto-adler.c | 0
.../{lustre => lnet}/libcfs/linux/linux-crypto.c | 0
.../{lustre => lnet}/libcfs/linux/linux-crypto.h | 0
.../{lustre => lnet}/libcfs/linux/linux-curproc.c | 0
.../{lustre => lnet}/libcfs/linux/linux-debug.c | 0
.../{lustre => lnet}/libcfs/linux/linux-mem.c | 0
.../{lustre => lnet}/libcfs/linux/linux-module.c | 0
.../{lustre => lnet}/libcfs/linux/linux-prim.c | 0
.../libcfs/linux/linux-tracefile.c | 0
.../lustre/{lustre => lnet}/libcfs/module.c | 0
.../staging/lustre/{lustre => lnet}/libcfs/prng.c | 0
.../lustre/{lustre => lnet}/libcfs/tracefile.c | 0
.../lustre/{lustre => lnet}/libcfs/tracefile.h | 0
.../lustre/{lustre => lnet}/libcfs/workitem.c | 0
drivers/staging/lustre/lustre/Kconfig | 2 +-
drivers/staging/lustre/lustre/Makefile | 2 +-
29 files changed, 17 insertions(+), 11 deletions(-)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/Makefile (93%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/debug.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/fail.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/hash.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/libcfs_cpu.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/libcfs_lock.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/libcfs_mem.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/libcfs_string.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-cpu.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-crypto-adler.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-crypto.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-crypto.h (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-curproc.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-debug.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-mem.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-module.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-prim.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/linux/linux-tracefile.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/module.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/prng.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/tracefile.c (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/tracefile.h (100%)
rename drivers/staging/lustre/{lustre => lnet}/libcfs/workitem.c (100%)
next reply other threads:[~2016-03-08 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 22:35 James Simmons [this message]
2016-03-08 22:35 ` [PATCH 1/4] staging: lustre: move libcfs to lnet layer James Simmons
2016-03-08 22:35 ` [PATCH 2/4] staging: lustre: fixup kernel Kconfig option LNET_MAX_PAYLOAD James Simmons
2016-03-08 22:35 ` [PATCH 3/4] staging: lustre: add help section of Kconfig config LNET James Simmons
2016-03-08 22:35 ` [PATCH 4/4] staging: lustre: make lustre dependent on LNet James Simmons
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=1457476529-27708-1-git-send-email-jsimmons@infradead.org \
--to=jsimmons@infradead.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
/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
all inboxes | Powered by JetHome®