> -----Original Message----- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Tuesday, April 03, 2018 7:06 AM > To: Jacob Keller <jacob.kel...@gmail.com> > Cc: Tal Gilboa <ta...@mellanox.com>; Tariq Toukan <tar...@mellanox.com>; > Keller, Jacob E <jacob.e.kel...@intel.com>; Ariel Elior > <ariel.el...@cavium.com>; > Ganesh Goudar <ganes...@chelsio.com>; Kirsher, Jeffrey T > <jeffrey.t.kirs...@intel.com>; everest-linux...@cavium.com; intel-wired- > l...@lists.osuosl.org; netdev@vger.kernel.org; linux-ker...@vger.kernel.org; > linux-...@vger.kernel.org > Subject: Re: [PATCH v5 03/14] PCI: Add pcie_bandwidth_capable() to compute > max supported link bandwidth > > On Mon, Apr 02, 2018 at 05:30:54PM -0700, Jacob Keller wrote: > > On Mon, Apr 2, 2018 at 7:05 AM, Bjorn Helgaas <helg...@kernel.org> wrote: > > > +/* PCIe speed to Mb/s reduced by encoding overhead */ > > > +#define PCIE_SPEED2MBS_ENC(speed) \ > > > + ((speed) == PCIE_SPEED_16_0GT ? (16000*(128/130)) : \ > > > + (speed) == PCIE_SPEED_8_0GT ? (8000*(128/130)) : \ > > > + (speed) == PCIE_SPEED_5_0GT ? (5000*(8/10)) : \ > > > + (speed) == PCIE_SPEED_2_5GT ? (2500*(8/10)) : \ > > > + 0) > > > + > > > > Should this be "(speed * x ) / y" instead? wouldn't they calculate > > 128/130 and truncate that to zero before multiplying by the speed? Or > > are compilers smart enough to do this the other way to avoid the > > losses? > > Yep, thanks for saving me yet more embarrassment.
That's what patch review is for :D Thanks, Jake
