From: 'Greg KH' <gregkh@linuxfoundation.org>
To: Steve Wise <swise@opengridcomputing.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs
Date: Sun, 5 Feb 2017 15:05:50 +0100 [thread overview]
Message-ID: <20170205140550.GA3173@kroah.com> (raw)
In-Reply-To: <026a01d27fb5$97910f00$c6b32d00$@opengridcomputing.com>
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
next prev parent reply other threads:[~2017-02-05 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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' [this message]
2017-02-06 14:59 ` Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170205140550.GA3173@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).