* [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs
@ 2017-02-03 17:04 Steve Wise
2017-02-05 10:28 ` Greg KH
0 siblings, 1 reply; 5+ messages in thread
From: Steve Wise @ 2017-02-03 17:04 UTC (permalink / raw)
To: stable
I forgot to add the stable Cc tag when I submitted this, but it is important to
get this patch into 4.9.x:
commit b414fa01c31318383ae29d9d23cb9ca4184bbd86
Author: Steve Wise <swise@opengridcomputing.com>
Date: Thu Dec 15 08:09:35 2016 -0800
iw_cxgb4: set correct FetchBurstMax for QPs
The current QP FetchBurstMax value is 256B, which
is incorrect since a WR can exceed that value. The
result being a partial WR fetched by hardware, and
a fatal "bad WR" error posted by the SGE.
So bump the FetchBurstMax to 512B.
Signed-off-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
I'm not sure if this is the correct way to request this, but I think I'm
following _option_2 from Documentation/stable_kernel_rules.txt.
Thanks,
Steve.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs
2017-02-03 17:04 [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs Steve Wise
@ 2017-02-05 10:28 ` Greg KH
2017-02-05 13:41 ` Steve Wise
0 siblings, 1 reply; 5+ messages in thread
From: Greg KH @ 2017-02-05 10:28 UTC (permalink / raw)
To: Steve Wise; +Cc: stable
On Fri, Feb 03, 2017 at 11:04:13AM -0600, Steve Wise wrote:
> I forgot to add the stable Cc tag when I submitted this, but it is important to
> get this patch into 4.9.x:
>
> commit b414fa01c31318383ae29d9d23cb9ca4184bbd86
> Author: Steve Wise <swise@opengridcomputing.com>
> Date: Thu Dec 15 08:09:35 2016 -0800
>
> iw_cxgb4: set correct FetchBurstMax for QPs
>
> The current QP FetchBurstMax value is 256B, which
> is incorrect since a WR can exceed that value. The
> result being a partial WR fetched by hardware, and
> a fatal "bad WR" error posted by the SGE.
>
> So bump the FetchBurstMax to 512B.
>
> Signed-off-by: Steve Wise <swise@opengridcomputing.com>
> Signed-off-by: Doug Ledford <dledford@redhat.com>
>
> I'm not sure if this is the correct way to request this, but I think I'm
> following _option_2 from Documentation/stable_kernel_rules.txt.
Now queued up. Are you sure this isn't also needed in the 4.4-stable
tree?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs
2017-02-05 10:28 ` Greg KH
@ 2017-02-05 13:41 ` Steve Wise
2017-02-05 14:05 ` 'Greg KH'
0 siblings, 1 reply; 5+ messages in thread
From: Steve Wise @ 2017-02-05 13:41 UTC (permalink / raw)
To: 'Greg KH'; +Cc: stable
> > commit b414fa01c31318383ae29d9d23cb9ca4184bbd86
> > Author: Steve Wise <swise@opengridcomputing.com>
> > Date: Thu Dec 15 08:09:35 2016 -0800
> >
> > iw_cxgb4: set correct FetchBurstMax for QPs
> >
> > The current QP FetchBurstMax value is 256B, which
> > is incorrect since a WR can exceed that value. The
> > result being a partial WR fetched by hardware, and
> > a fatal "bad WR" error posted by the SGE.
> >
> > So bump the FetchBurstMax to 512B.
> >
> > Signed-off-by: Steve Wise <swise@opengridcomputing.com>
> > Signed-off-by: Doug Ledford <dledford@redhat.com>
> >
> > I'm not sure if this is the correct way to request this, but I think I'm
> > following _option_2 from Documentation/stable_kernel_rules.txt.
>
> Now queued up. Are you sure this isn't also needed in the 4.4-stable
> tree?
>
Hey Greg, At first, I didn't think it is needed because, while the bug is
indeed present in that code, it is only exposed (and causes problems) with
the new T6 hardware. But now I think I'd like the fix pulled in 4.4-stable
to avoid any issues if T6 support is pulled into that base.
Thanks!
Steve
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs
2017-02-05 13:41 ` Steve Wise
@ 2017-02-05 14:05 ` 'Greg KH'
2017-02-06 14:59 ` Steve Wise
0 siblings, 1 reply; 5+ messages in thread
From: 'Greg KH' @ 2017-02-05 14:05 UTC (permalink / raw)
To: Steve Wise; +Cc: stable
On Sun, Feb 05, 2017 at 07:41:45AM -0600, Steve Wise wrote:
> > > commit b414fa01c31318383ae29d9d23cb9ca4184bbd86
> > > Author: Steve Wise <swise@opengridcomputing.com>
> > > Date: Thu Dec 15 08:09:35 2016 -0800
> > >
> > > iw_cxgb4: set correct FetchBurstMax for QPs
> > >
> > > The current QP FetchBurstMax value is 256B, which
> > > is incorrect since a WR can exceed that value. The
> > > result being a partial WR fetched by hardware, and
> > > a fatal "bad WR" error posted by the SGE.
> > >
> > > So bump the FetchBurstMax to 512B.
> > >
> > > Signed-off-by: Steve Wise <swise@opengridcomputing.com>
> > > Signed-off-by: Doug Ledford <dledford@redhat.com>
> > >
> > > I'm not sure if this is the correct way to request this, but I think I'm
> > > following _option_2 from Documentation/stable_kernel_rules.txt.
> >
> > Now queued up. Are you sure this isn't also needed in the 4.4-stable
> > tree?
> >
>
> Hey Greg, At first, I didn't think it is needed because, while the bug is
> indeed present in that code, it is only exposed (and causes problems) with
> the new T6 hardware. But now I think I'd like the fix pulled in 4.4-stable
> to avoid any issues if T6 support is pulled into that base.
How would I pull "T6" support into that kernel? I'm guessing that's a
much larger issue and isn't something that would normally happen in a
stable kernel release?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs
2017-02-05 14:05 ` 'Greg KH'
@ 2017-02-06 14:59 ` Steve Wise
0 siblings, 0 replies; 5+ messages in thread
From: Steve Wise @ 2017-02-06 14:59 UTC (permalink / raw)
To: 'Greg KH'; +Cc: stable
>>> Now queued up. Are you sure this isn't also needed in the 4.4-stable
>>> tree?
>>>
>> Hey Greg, At first, I didn't think it is needed because, while the bug is
>> indeed present in that code, it is only exposed (and causes problems) with
>> the new T6 hardware. But now I think I'd like the fix pulled in 4.4-stable
>> to avoid any issues if T6 support is pulled into that base.
> How would I pull "T6" support into that kernel? I'm guessing that's a
> much larger issue and isn't something that would normally happen in a
> stable kernel release?
>
I guess that won't happen. To enable the T6 adapter several commits to
drivers/net/ethernet/chelsio/cxgb4 and drivers/infiniband/hw/cxgb4 would
have to flow into stable, and I guess that will not happen. Ok, so no
4.4-stable.
Thanks,
Steve.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-02-06 14:59 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-03 17:04 [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs Steve Wise
2017-02-05 10:28 ` Greg KH
2017-02-05 13:41 ` Steve Wise
2017-02-05 14:05 ` 'Greg KH'
2017-02-06 14:59 ` Steve Wise
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).