lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <40F65EF2B5E2254199711F58E3ACB84D830FEEF3@MX104CL02.corp.emc.com>
Date:	Tue, 9 Jun 2015 16:59:57 +0000
From:	"Hubbe, Allen" <Allen.Hubbe@....com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
CC:	"linux-ntb@...glegroups.com" <linux-ntb@...glegroups.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Jon Mason <jdmason@...zu.us>, Dave Jiang <dave.jiang@...el.com>
Subject: RE: [PATCH v3 09/18] NTB: Add parameters for Intel SNB B2B addresses

From: Bjorn Helgaas [mailto:bhelgaas@...gle.com]
> On Tue, Jun 09, 2015 at 05:44:36AM -0400, Allen Hubbe wrote:
> > Add module parameters for the addresses to be used in b2b topology.
> 
> What does "b2b" mean?

In this case it means back-to-back, referring to the topology connecting the ntb devices.  There are two ntb devices connected to each other, secondary side to secondary side, or back-to-back.

The terminology is not entirely unambiguous, unfortunately.  In the glossary of an Intel doc, it is defined as above, as back-to-back.  PLX doesn't ever use the term b2b that I could find, but it uses the term back-to-back instead referring to the two internal endpoints of one ntb device.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ