[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALx6S34zw7S+8rB9nuBtbzZ6JkcVreHTwJZrXftHdfmKLF3knQ@mail.gmail.com>
Date: Fri, 13 Jan 2017 15:07:51 -0800
From: Tom Herbert <tom@...bertland.com>
To: Rick Jones <rick.jones2@....com>
Cc: Saeed Mahameed <saeedm@....mellanox.co.il>,
Leon Romanovsky <leon@...nel.org>,
David Miller <davem@...emloft.net>,
Saeed Mahameed <saeedm@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
linux-rdma@...r.kernel.org
Subject: Re: [pull request][for-next] Mellanox mlx5 Reorganize core driver
directory layout
On Fri, Jan 13, 2017 at 2:59 PM, Rick Jones <rick.jones2@....com> wrote:
> On 01/13/2017 02:56 PM, Tom Herbert wrote:
>>
>> On Fri, Jan 13, 2017 at 2:45 PM, Saeed Mahameed
>>>
>>> what configuration are you running ? what traffic ?
>>>
>> Nothing fancy. 8 queues and 20 concurrent netperf TCP_STREAMs trips
>> it. Not a lot of them, but I don't think we really should ever see
>> these errors.
>
>
> Straight-up defaults with netperf, or do you use specific -s/S or -m/M
> options?
>
./super_netperf_tput 20 -H test001 -l 100 -t TCP_STREAM
> happy benchmarking,
>
> rick jones
>
Powered by blists - more mailing lists