> Il giorno 10 mag 2018, alle ore 18:12, Bart Van Assche
> ha scritto:
>
> On Fri, 2018-05-04 at 22:11 +0200, Paolo Valente wrote:
>>> Il giorno 30 mar 2018, alle ore 18:57, Bart Van Assche
>>> ha scritto:
>>>
>>> On Fri, 2018-03-30 at 10:23 +0200, Paolo Valente wrote:
Still 4.16-rc1,
On Fri, 2018-05-04 at 22:11 +0200, Paolo Valente wrote:
> > Il giorno 30 mar 2018, alle ore 18:57, Bart Van Assche
> > ha scritto:
> >
> > On Fri, 2018-03-30 at 10:23 +0200, Paolo Valente wrote:
> > > Still 4.16-rc1, being that the version for which you reported this
> > > issue in the first pla
On Thu, 2018-05-10 at 15:16 +, Bart Van Assche wrote:
> On Fri, 2018-05-04 at 16:42 -0400, Laurence Oberman wrote:
> > I was never able to reproduce Barts original issue using his tree
> > and
> > actual mlx5/cx4 hardware and ibsrp
> > I enabled BFQ with no other special tuning for the moath an
> Il giorno 10 mag 2018, alle ore 17:16, Bart Van Assche
> ha scritto:
>
> On Fri, 2018-05-04 at 16:42 -0400, Laurence Oberman wrote:
>> I was never able to reproduce Barts original issue using his tree and
>> actual mlx5/cx4 hardware and ibsrp
>> I enabled BFQ with no other special tuning for
On Fri, 2018-05-04 at 16:42 -0400, Laurence Oberman wrote:
> I was never able to reproduce Barts original issue using his tree and
> actual mlx5/cx4 hardware and ibsrp
> I enabled BFQ with no other special tuning for the moath and subpaths.
> I was waiting for him to come back from vacation to chec
On Fri, 2018-05-04 at 22:11 +0200, Paolo Valente wrote:
> > Il giorno 30 mar 2018, alle ore 18:57, Bart Van Assche > c...@wdc.com> ha scritto:
> >
> > On Fri, 2018-03-30 at 10:23 +0200, Paolo Valente wrote:
> > > Still 4.16-rc1, being that the version for which you reported
> > > this
> > > issue
> Il giorno 30 mar 2018, alle ore 18:57, Bart Van Assche
> ha scritto:
>
> On Fri, 2018-03-30 at 10:23 +0200, Paolo Valente wrote:
>> Still 4.16-rc1, being that the version for which you reported this
>> issue in the first place.
>
> A vanilla v4.16-rc1 kernel is not sufficient to run the srp
> Il giorno 01 apr 2018, alle ore 10:56, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 30 mar 2018, alle ore 18:57, Bart Van Assche
>> ha scritto:
>>
>> On Fri, 2018-03-30 at 10:23 +0200, Paolo Valente wrote:
>>> Still 4.16-rc1, being that the version for which you reported this
>>> issu
> Il giorno 30 mar 2018, alle ore 18:57, Bart Van Assche
> ha scritto:
>
> On Fri, 2018-03-30 at 10:23 +0200, Paolo Valente wrote:
>> Still 4.16-rc1, being that the version for which you reported this
>> issue in the first place.
>
> A vanilla v4.16-rc1 kernel is not sufficient to run the srp
On Fri, 2018-03-30 at 10:23 +0200, Paolo Valente wrote:
> Still 4.16-rc1, being that the version for which you reported this
> issue in the first place.
A vanilla v4.16-rc1 kernel is not sufficient to run the srp-test software
since RDMA/CM support for the SRP target driver is missing from that ke
+Jens, Mike
> Il giorno 30 mar 2018, alle ore 01:16, Bart Van Assche
> ha scritto:
>
> On Thu, 2018-03-29 at 11:02 +0200, Paolo Valente wrote:
>>> Il giorno 01 mar 2018, alle ore 02:35, Bart Van Assche
>>> ha scritto:
>>> Thank you for having shared your kernel config off-list. After having
>
On Thu, 2018-03-29 at 11:02 +0200, Paolo Valente wrote:
> > Il giorno 01 mar 2018, alle ore 02:35, Bart Van Assche
> > ha scritto:
> > Thank you for having shared your kernel config off-list. After having
> > made the following changes to your kernel config I was able to run the
> > srp-test soft
On Fri, 2018-02-16 at 08:39 +0100, Paolo Valente wrote:
> after enabling the listing options in your list, and a few other
> related options, such iblock support, I get this:
>
> $ sudo ./run_tests -c -d -r 10 -t 02-mq -e bfq
> Unloaded the ib_srpt kernel module
> Unloaded the rdma_rxe kernel modu
On Fri, 2018-02-16 at 08:39 +0100, Paolo Valente wrote:
> after enabling the listing options in your list, and a few other
> related options, such iblock support, I get this:
>
> $ sudo ./run_tests -c -d -r 10 -t 02-mq -e bfq
> Unloaded the ib_srpt kernel module
> Unloaded the rdma_rxe kernel modu
> Il giorno 14 feb 2018, alle ore 19:11, Bart Van Assche
> ha scritto:
>
> On 02/14/18 09:55, Paolo Valente wrote:
>> After following all of them (and taking some other step needed), I
>> invoked:
>> sudo ./run_tests -c -d -r 10 -t 02-mq -e bfq
>> But I got the following:
>> ./lib/functions: r
On 02/14/18 09:55, Paolo Valente wrote:
After following all of them (and taking some other step needed), I
invoked:
sudo ./run_tests -c -d -r 10 -t 02-mq -e bfq
But I got the following:
./lib/functions: riga 34: /sys/class/block/ram0/size: No such file or directory
./lib/functions: riga 34: * 51
> Il giorno 13 feb 2018, alle ore 19:47, Bart Van Assche
> ha scritto:
>
> On Tue, 2018-02-13 at 19:38 +0100, Paolo Valente wrote:
>> as a first attempt, I've followed your steps, but got:
>> Error: could not find sg_reset
>
> Please install the sg3_utils package. Every Linux distro I know of
On Tue, 2018-02-13 at 19:38 +0100, Paolo Valente wrote:
> as a first attempt, I've followed your steps, but got:
> Error: could not find sg_reset
Please install the sg3_utils package. Every Linux distro I know of supports that
package. And in case you would like to install it from source, the sour
> Il giorno 12 feb 2018, alle ore 17:31, Bart Van Assche
> ha scritto:
>
> On 02/11/18 23:35, Paolo Valente wrote:
>> Also this smells a little bit like some spurious elevator call.
>> Unfortunately I have no clue on the cause. To go on, I need at least
>> to reproduce it. In this respect: B
On 02/11/18 23:35, Paolo Valente wrote:
Also this smells a little bit like some spurious elevator call.
Unfortunately I have no clue on the cause. To go on, I need at least
to reproduce it. In this respect: Bart, could you please tell me how
to setup the offending configuration, and to cause th
> Il giorno 09 feb 2018, alle ore 20:18, Jens Axboe ha
> scritto:
>
> On 2/9/18 12:14 PM, Bart Van Assche wrote:
>> On 02/09/18 10:58, Jens Axboe wrote:
>>> On 2/9/18 11:54 AM, Bart Van Assche wrote:
Hello Paolo,
If I enable the BFQ scheduler for a dm-mpath device then a kernel
On 2/9/18 12:14 PM, Bart Van Assche wrote:
> On 02/09/18 10:58, Jens Axboe wrote:
>> On 2/9/18 11:54 AM, Bart Van Assche wrote:
>>> Hello Paolo,
>>>
>>> If I enable the BFQ scheduler for a dm-mpath device then a kernel oops
>>> appears (see also below). This happens systematically with Linus' tree
On 02/09/18 10:58, Jens Axboe wrote:
On 2/9/18 11:54 AM, Bart Van Assche wrote:
Hello Paolo,
If I enable the BFQ scheduler for a dm-mpath device then a kernel oops
appears (see also below). This happens systematically with Linus' tree from
this morning (commit 54ce685cae30) merged with Jens' fo
On 2/9/18 11:54 AM, Bart Van Assche wrote:
> Hello Paolo,
>
> If I enable the BFQ scheduler for a dm-mpath device then a kernel oops
> appears (see also below). This happens systematically with Linus' tree from
> this morning (commit 54ce685cae30) merged with Jens' for-linus branch (commit
> a7877
24 matches
Mail list logo