From: Doug Oucharek <doucharek@cray.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Christoph Hellwig <hch@infradead.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleg Drokin <oleg.drokin@intel.com>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>,
fsdevel <linux-fsdevel@vger.kernel.org>,
lustre-devel <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [PATCH] staging: lustre: delete the filesystem from the tree.
Date: Fri, 1 Jun 2018 18:25:24 +0000 [thread overview]
Message-ID: <29ACF5A8-7608-46BB-8191-E3FEB77D0F24@cray.com> (raw)
In-Reply-To: <E5BF8501-35EB-4DDF-ADBE-6016CF31A502@dilger.ca>
Would it makes sense to land LNet and LNDs on their own first? Get the networking house in order first before layering on the file system?
Doug
> On Jun 1, 2018, at 11:20 AM, Andreas Dilger <adilger@dilger.ca> wrote:
>
> On Jun 1, 2018, at 7:41 AM, Christoph Hellwig <hch@infradead.org> wrote:
>>
>> Thanks,
>>
>> all that churn without much visible progress to a mergeable codebase
>> was really ennoying.
>>
>> I'd recommend if people want to merge lustre they start with a managable
>> subset first, e.g. the fs client code with simple IP-only networking.
>
> Adding or removing the IB networking makes basically no difference to the
> code size. This would also make the client much less useful, since a large
> number of sites use Lustre with IB networks.
>
> Cheers, Andreas
>
>
>
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
next prev parent reply other threads:[~2018-06-01 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 9:11 [PATCH] staging: lustre: delete the filesystem from the tree Greg Kroah-Hartman
2018-06-01 11:41 ` Christoph Hellwig
2018-06-01 18:20 ` Andreas Dilger
2018-06-01 18:25 ` Doug Oucharek [this message]
2018-06-01 23:19 ` [lustre-devel] " NeilBrown
2018-06-03 20:34 ` Dilger, Andreas
2018-06-04 3:54 ` NeilBrown
2018-06-04 3:59 ` Alexey Lyashkov
2018-06-04 4:15 ` Andreas Dilger
2018-06-04 4:17 ` Alexey Lyashkov
2018-06-01 18:30 ` Andreas Dilger
2018-06-01 18:41 ` Oleg Drokin
2018-06-01 19:08 ` Greg Kroah-Hartman
2018-06-04 7:09 ` Christoph Hellwig
2018-06-04 7:14 ` Greg Kroah-Hartman
2018-06-02 0:28 ` [lustre-devel] " NeilBrown
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=29ACF5A8-7608-46BB-8191-E3FEB77D0F24@cray.com \
--to=doucharek@cray.com \
--cc=adilger@dilger.ca \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=selinux@tycho.nsa.gov \
/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 NNTP newsgroup(s).