On Mon, Jun 04, 2018 at 12:09:22AM -0700, Christoph Hellwig wrote:
> On Fri, Jun 01, 2018 at 09:08:39PM +0200, Greg Kroah-Hartman wrote:
> > Please, compare yourself to orangefs. That is the perfect example of
> > how to do everything right. They got their code into staging, cleaned
> > it up, ta
On Fri, Jun 01, 2018 at 09:08:39PM +0200, Greg Kroah-Hartman wrote:
> Please, compare yourself to orangefs. That is the perfect example of
> how to do everything right. They got their code into staging, cleaned
> it up, talked to us about what was needed to do to get the remaining
> bits in prope
On Jun 3, 2018, at 9:59 PM, Alexey Lyashkov wrote:
>
>> On Sun, Jun 03 2018, Dilger, Andreas wrote:
>>
>>> LNet is originally based on a high-performance networking stack called
>>> Portals (v3, http://www.cs.sandia.gov/Portals/), with additions for LNet
>>> routing to allow cross-network bridgi
> 4 июня 2018 г., в 7:15, Andreas Dilger написал(а):
>
> On Jun 3, 2018, at 9:59 PM, Alexey Lyashkov wrote:
>>
>>> On Sun, Jun 03 2018, Dilger, Andreas wrote:
>>>
LNet is originally based on a high-performance networking stack called
Portals (v3, http://www.cs.sandia.gov/Portals/),
> 4 июня 2018 г., в 6:54, NeilBrown написал(а):
>
> On Sun, Jun 03 2018, Dilger, Andreas wrote:
>
>> On Jun 1, 2018, at 17:19, NeilBrown wrote:
>>>
>>> On Fri, Jun 01 2018, Doug Oucharek wrote:
>>>
Would it makes sense to land LNet and LNDs on their own first? Get
the networking h
On Sun, Jun 03 2018, Dilger, Andreas wrote:
> On Jun 1, 2018, at 17:19, NeilBrown wrote:
>>
>> On Fri, Jun 01 2018, Doug Oucharek wrote:
>>
>>> 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?
>>
On Jun 1, 2018, at 17:19, NeilBrown wrote:
>
> On Fri, Jun 01 2018, Doug Oucharek wrote:
>
>> 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?
>
> I'd like to turn that question on it's head:
> Do
On Fri, Jun 01 2018, Greg Kroah-Hartman wrote:
>
> So, let's just delete the whole mess. Now the lustre developers can go
> off and work in their out-of-tree codebase and not have to worry about
> providing valid changelog entries and breaking their patches up into
> logical pieces.
I find it in
On Fri, Jun 01 2018, Doug Oucharek wrote:
> 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?
I'd like to turn that question on it's head:
Do we need LNet and LNDs? What value do they provide?
(this i
> On Jun 1, 2018, at 2:30 PM, Andreas Dilger wrote:
>
> On Jun 1, 2018, at 5:11 AM, Greg Kroah-Hartman
> wrote:
>>
>> The Lustre filesystem has been in the kernel tree for over 5 years now.
>> While it has been an endless source of enjoyment for new kernel
>> developers learning how to do bas
On Fri, Jun 01, 2018 at 02:30:49PM -0400, Andreas Dilger wrote:
> On Jun 1, 2018, at 5:11 AM, Greg Kroah-Hartman
> wrote:
> >
> > The Lustre filesystem has been in the kernel tree for over 5 years now.
> > While it has been an endless source of enjoyment for new kernel
> > developers learning ho
On Jun 1, 2018, at 5:11 AM, Greg Kroah-Hartman
wrote:
>
> The Lustre filesystem has been in the kernel tree for over 5 years now.
> While it has been an endless source of enjoyment for new kernel
> developers learning how to do basic codingstyle cleanups, as well as an
> semi-entertaining source
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 wrote:
>
> On Jun 1, 2018, at 7:41 AM, Christoph Hellwig wrote:
>>
>> Thanks,
>>
>> all that churn w
On Jun 1, 2018, at 7:41 AM, Christoph Hellwig 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-on
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.
___
devel ma
The Lustre filesystem has been in the kernel tree for over 5 years now.
While it has been an endless source of enjoyment for new kernel
developers learning how to do basic codingstyle cleanups, as well as an
semi-entertaining source of bewilderment from the vfs developers any
time they have looked
16 matches
Mail list logo
