[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4f679cd-739b-fd80-8344-7da475937835@deltatee.com>
Date: Tue, 17 Dec 2019 09:42:48 -0700
From: Logan Gunthorpe <logang@...tatee.com>
To: Jiasen Lin <linjiasen@...on.cn>, linux-kernel@...r.kernel.org,
linux-ntb@...glegroups.com, jdmason@...zu.us
Cc: allenbh@...il.com, dave.jiang@...el.com, sanju.mehta@....com
Subject: Re: [PATCH] NTB: ntb_perf: Add more debugfs entries for ntb_perf
On 2019-12-16 7:42 p.m., Jiasen Lin wrote:
> Currently, read input and output buffer is not supported yet in
> debugfs of ntb_perf. We can not confirm whether the output data is
> transmitted to the input buffer at peer memory through NTB.
>
> This patch add new entries in debugfs which implement interface to read
> a part of input and out buffer. User can dump output and input data at
> local and peer system by hexdump command, and then compare them manually.
Do we even initialize inbuf and outbuf? Probably not a good idea to
expose them to userspace if it's not initialized.
Really, ntb_tool should be used to check if memory windows work,
ntb_perf is just to see the maximum transfer rate.
Logan
Powered by blists - more mailing lists