[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0d106ece-4669-389d-da30-63a630ca625c@mellanox.com>
Date: Tue, 3 Apr 2018 08:43:27 +0300
From: Alex Vesker <valex@...lanox.com>
To: Jiri Pirko <jiri@...nulli.us>, 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>
Subject: Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware
dump in second kernel
On 4/2/2018 12:12 PM, Jiri Pirko wrote:
> 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.
I didn't check the performance for such a large snapshot.
From my measurement it takes 0.09s for 1 MB of data this means
about ~3m.
This can be tuned and improved since this is a socket application.
>> Andrew
Powered by blists - more mailing lists