All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve Wise" <swise@opengridcomputing.com>
To: "'Greg KH'" <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>
Subject: RE: [PATCH] iw_cxgb4: set correct FetchBurstMax for QPs
Date: Sun, 5 Feb 2017 07:41:45 -0600	[thread overview]
Message-ID: <026a01d27fb5$97910f00$c6b32d00$@opengridcomputing.com> (raw)
In-Reply-To: <20170205102847.GA28076@kroah.com>

> > 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
 



  reply	other threads:[~2017-02-05 14:06 UTC|newest]

Thread overview: 7+ 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 [this message]
2017-02-05 14:05     ` 'Greg KH'
2017-02-06 14:59       ` Steve Wise
  -- strict thread matches above, loose matches on Subject: below --
2016-12-15 16:09 Steve Wise
     [not found] ` <20161215210330.81B67E08C3-/5N3P9jjx0xzbRFIqnYvSA@public.gmane.org>
2016-12-18 18:36   ` Doug Ledford

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='026a01d27fb5$97910f00$c6b32d00$@opengridcomputing.com' \
    --to=swise@opengridcomputing.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.