From: James Simmons <jsimmons@infradead.org>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] linux lustre client progress
Date: Mon, 7 Jan 2019 03:11:13 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.1901070208080.26665@casper.infradead.org> (raw)
Over the last few weeks the final major bugs have been resolved for the
linux lustre client as well as a port of PFL. Once these patches are
merged the client will be at a 2.10 LTS release level. A few minor
patches are still out standing but they need more work before being
acceptable in the kernel tree. The remaining test failures are the
same ones seen in the latest OpenSFS tree testing.
Before we jump into 2.11 porting I'm thinking some house cleaning with
checkpatch etc and then moving lustre out of the staging tree to
prepare for its eventual merger upstream. As for 2.11 I started to
look at the what is missing and outside of the DoM feature most
things have landed to the linux client. In fact the next patch missing
in the git logs is the first DoM patch. Dynamic LNet discovery already
has been landed so we are in good shape :-)
reply other threads:[~2019-01-07 3:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.21.1901070208080.26665@casper.infradead.org \
--to=jsimmons@infradead.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).