From: Ben Evans <bevans@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] porting Lustre server to RHEL6.7 distro running a kernel.org linux-3.12.39
Date: Mon, 2 Nov 2015 19:25:54 +0000 [thread overview]
Message-ID: <D25D229F.28B1%jevans@cray.com> (raw)
In-Reply-To: <5637B5CB.9090106@cray.com>
Using ZFS as a backing filesystem may be a simpler way to go here if you want to stay with kernel.org. The lustre server + ZFS is patchless, and if you?re writing a new LND, you probably don?t care about the backing filesystem anyway.
-Ben Evans
From: lustre-devel <lustre-devel-bounces at lists.lustre.org<mailto:lustre-devel-bounces@lists.lustre.org>> on behalf of Patrick Farrell <paf at cray.com<mailto:paf@cray.com>>
Date: Monday, November 2, 2015 at 3:13 PM
To: "lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>" <lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>>
Subject: Re: [lustre-devel] porting Lustre server to RHEL6.7 distro running a kernel.org linux-3.12.39
Stan,
Why not work with the CentOS 7 kernel on the server anyway? Is something your LND needs not available? CentOS 7 is freely available and isn't far off in terms of kernel version from 3.12.
You may be hard pressed to get useful advice on changing the ldiskfs patch series, that has the potential to be a pretty big job.
Regards,
- Patrick Farrell
On 11/02/2015 01:05 PM, Smith, Stan wrote:
Hello,
I?m currently unable to search the lustre-devel archives + 1st post to this list.
Having read lustre documentation I find only references to building lustre server for stock ?distro? kernels.
Does someone have suggestions on how to patch ldiskfs for a kernel.org kernel?..specifically weeding out RHEL/SLES/* distro FS enhancements from a kernel.org base?
I have written a Reliable Datagram LND which passes the LNet selftests (client lustre build) now entering the world of lustre server building.
Patching the kernel.org kernel for lustre server was fairly straightforward, creating the patch series for ldiskfs is another story.
Thanks,
Stan.
_______________________________________________
lustre-devel mailing list
lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20151102/89540b8b/attachment.htm>
next prev parent reply other threads:[~2015-11-02 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 19:05 [lustre-devel] porting Lustre server to RHEL6.7 distro running a kernel.org linux-3.12.39 Smith, Stan
2015-11-02 19:13 ` Patrick Farrell
2015-11-02 19:25 ` Ben Evans [this message]
2015-11-02 20:46 ` Smith, Stan
2015-11-02 20:49 ` Ben Evans
2015-11-02 19:35 ` Smith, Stan
2015-11-02 19:45 ` Patrick Farrell
2015-11-02 20:25 ` Rick Wagner
2015-11-02 20:52 ` Smith, Stan
2015-11-02 21:07 ` Colin Faber
2015-11-02 21:24 ` Rick Wagner
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=D25D229F.28B1%jevans@cray.com \
--to=bevans@cray.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.