Jeff Squyres (jsquyres) <[email protected]> wrote: > Sure. For a little background, the 2nd-generation Cisco VIC has been > available > since last year (IIRC): http://www.cisco.com/en/US/products/ps10277 > /prod_module_series_home.html. It's a converged 10G Ethernet adapter > available > in a variety of form factors (e.g., 2x10G on PCIe and Mezz).
> After some off-list discussion with Roland, we chose to create new IBV_*_USNIC > enums because none of the current enums were accurate for our device. It's an > Ethernet NIC, but it's not an RNIC. It's an Ethernet-based transport, but > it's not > iWARP. > > The reason we're asking for these IBV_*_USNIC enums now -- before we've > submitted the driver -- is because we're targeting getting our driver > included in RHEL 6.5. There's a bit of a chicken-and-egg issue here: they'll > accept our patches for a new hardware driver while that driver is being > worked upstream. But they (rightfully) won't accept patches to IB core and > libibverbs until they've been vetted by the community. Hence, even though > our driver is slowly working its way through QA and not available yet, we > wanted to submit these new enums upstream for community approval so that they > can be included in RHEL 6.5. > Does that help? yes it does, but I still think we need to see the driver code in order to conduct proper /better review and maybe even accept the proposed changes to the IB core. You can submit it as RFC which means "you can look on it, and give me comments, but don't pick it up yet" Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
