From: Jon Mason <jdmason@kudzu.us>
To: Allen Hubbe <Allen.Hubbe@dell.com>
Cc: 'Logan Gunthorpe' <logang@deltatee.com>,
linux-ntb@googlegroups.com, 'Dave Jiang' <dave.jiang@intel.com>
Subject: Re: [PATCH] ntb_transport: fix bug calculating num_qps_mw
Date: Fri, 9 Jun 2017 17:09:09 -0400 [thread overview]
Message-ID: <20170609210908.GC9847@kudzu.us> (raw)
In-Reply-To: <000101d2dec6$0648f060$12dad120$@dell.com>
On Tue, Jun 06, 2017 at 09:08:43AM -0400, Allen Hubbe wrote:
> From: Logan Gunthorpe
> > A divide by zero error occurs if qp_count is less than mw_count because
> > num_qps_mw is calculated to be zero. The calculation appears to be
> > incorrect.
> >
> > The requirement is for num_qps_mw to be set to qp_count / mw_count
> > with any remainder divided among the earlier mws.
> >
> > For example, if mw_count is 5 and qp_count is 12 then mws 0 and 1
> > will have 3 qps per window and mws 2 through 4 will have 2 qps per window.
> > Thus, when mw_num < qp_count % mw_count, num_qps_mw is 1 higher
> > than when mw_num >= qp_count.
> >
> > Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> > Cc: Jon Mason <jdmason@kudzu.us>
> > Cc: Dave Jiang <dave.jiang@intel.com>
> > Cc: Allen Hubbe <Allen.Hubbe@emc.com>
>
> Acked-by: Allen Hubbe <Allen.Hubbe@dell.com>
Adding to my ntb branch with the following line:
Fixes: e26a5843f7f5 ("NTB: Split ntb_hw_intel and ntb_transport drivers")
This enables the stable kernels it is a bug fix and to pick it up.
Thanks,
Jon
>
> > ---
> > drivers/ntb/ntb_transport.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
> > index 0a778d2cab94..5b6b00ea6ed9 100644
> > --- a/drivers/ntb/ntb_transport.c
> > +++ b/drivers/ntb/ntb_transport.c
> > @@ -623,7 +623,7 @@ static int ntb_transport_setup_qp_mw(struct ntb_transport_ctx *nt,
> > if (!mw->virt_addr)
> > return -ENOMEM;
> >
> > - if (qp_count % mw_count && mw_num + 1 < qp_count / mw_count)
> > + if (mw_num < qp_count % mw_count)
> > num_qps_mw = qp_count / mw_count + 1;
> > else
> > num_qps_mw = qp_count / mw_count;
> > @@ -1000,7 +1000,7 @@ static int ntb_transport_init_queue(struct ntb_transport_ctx *nt,
> > qp->event_handler = NULL;
> > ntb_qp_link_down_reset(qp);
> >
> > - if (qp_count % mw_count && mw_num + 1 < qp_count / mw_count)
> > + if (mw_num < qp_count % mw_count)
> > num_qps_mw = qp_count / mw_count + 1;
> > else
> > num_qps_mw = qp_count / mw_count;
> > --
> > 2.11.0
>
>
next prev parent reply other threads:[~2017-06-09 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 20:00 [PATCH] ntb_netdev: set the net_device's parent Logan Gunthorpe
2017-06-05 20:00 ` [PATCH] ntb_transport: fix qp count bug Logan Gunthorpe
2017-06-06 13:08 ` Allen Hubbe
2017-06-09 21:09 ` Jon Mason
2017-06-05 20:00 ` [PATCH] ntb_transport: fix bug calculating num_qps_mw Logan Gunthorpe
2017-06-06 13:08 ` Allen Hubbe
2017-06-09 21:09 ` Jon Mason [this message]
2017-06-06 13:08 ` [PATCH] ntb_netdev: set the net_device's parent Allen Hubbe
2017-06-09 21:12 ` Jon Mason
2017-06-09 21:51 ` Logan Gunthorpe
2017-06-09 21:56 ` Jon Mason
2017-06-09 22:51 ` Logan Gunthorpe
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=20170609210908.GC9847@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Allen.Hubbe@dell.com \
--cc=dave.jiang@intel.com \
--cc=linux-ntb@googlegroups.com \
--cc=logang@deltatee.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