Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Logan Gunthorpe
On 01/08/17 12:16 PM, Jon Mason wrote: > On Tue, Aug 01, 2017 at 12:09:18PM -0600, Logan Gunthorpe wrote: >> >> On 01/08/17 12:07 PM, Jon Mason wrote: >>> On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: After the link tests, there is a race on one side of the test for

Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Logan Gunthorpe
On 01/08/17 12:16 PM, Jon Mason wrote: > On Tue, Aug 01, 2017 at 12:09:18PM -0600, Logan Gunthorpe wrote: >> >> On 01/08/17 12:07 PM, Jon Mason wrote: >>> On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: After the link tests, there is a race on one side of the test for

Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Jon Mason
On Tue, Aug 01, 2017 at 12:09:18PM -0600, Logan Gunthorpe wrote: > > On 01/08/17 12:07 PM, Jon Mason wrote: > > On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: > >> After the link tests, there is a race on one side of the test for > >> the link coming up. It's possible, in some

Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Jon Mason
On Tue, Aug 01, 2017 at 12:09:18PM -0600, Logan Gunthorpe wrote: > > On 01/08/17 12:07 PM, Jon Mason wrote: > > On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: > >> After the link tests, there is a race on one side of the test for > >> the link coming up. It's possible, in some

Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Logan Gunthorpe
On 01/08/17 12:07 PM, Jon Mason wrote: > On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: >> After the link tests, there is a race on one side of the test for >> the link coming up. It's possible, in some cases, for the test script >> to write to the 'peer_trans' files before the

Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Logan Gunthorpe
On 01/08/17 12:07 PM, Jon Mason wrote: > On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: >> After the link tests, there is a race on one side of the test for >> the link coming up. It's possible, in some cases, for the test script >> to write to the 'peer_trans' files before the

Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Jon Mason
On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: > After the link tests, there is a race on one side of the test for > the link coming up. It's possible, in some cases, for the test script > to write to the 'peer_trans' files before the link has come up. > > To fix this, we simply

Re: [PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-08-01 Thread Jon Mason
On Tue, Jul 25, 2017 at 02:57:42PM -0600, Logan Gunthorpe wrote: > After the link tests, there is a race on one side of the test for > the link coming up. It's possible, in some cases, for the test script > to write to the 'peer_trans' files before the link has come up. > > To fix this, we simply

[PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-07-25 Thread Logan Gunthorpe
After the link tests, there is a race on one side of the test for the link coming up. It's possible, in some cases, for the test script to write to the 'peer_trans' files before the link has come up. To fix this, we simply use the link event file to ensure both sides see the link as up before

[PATCH v3 05/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

2017-07-25 Thread Logan Gunthorpe
After the link tests, there is a race on one side of the test for the link coming up. It's possible, in some cases, for the test script to write to the 'peer_trans' files before the link has come up. To fix this, we simply use the link event file to ensure both sides see the link as up before