[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180402091232.GE3313@nanopsycho>
Date: Mon, 2 Apr 2018 11:12:32 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Andrew Lunn <andrew@...n.ch>
Cc: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>,
netdev@...r.kernel.org, linux-fsdevel@...r.kernel.org,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
davem@...emloft.net, viro@...iv.linux.org.uk,
ebiederm@...ssion.com, stephen@...workplumber.org,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
ganeshgr@...lsio.com, nirranjan@...lsio.com, indranil@...lsio.com,
valex@...lanox.com
Subject: Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware
dump in second kernel
Fri, Mar 30, 2018 at 05:11:29PM CEST, andrew@...n.ch wrote:
>> Please see:
>> http://patchwork.ozlabs.org/project/netdev/list/?series=36524
>>
>> I bevieve that the solution in the patchset could be used for
>> your usecase too.
>
>Hi Jiri
>
>https://lkml.org/lkml/2018/3/20/436
>
>How well does this API work for a 2Gbyte snapshot?
Ccing Alex who did the tests.
>
> Andrew
Powered by blists - more mailing lists