[dpdk-dev] [RFC PATCH 2/2] ixgbe: release software locked semaphores on initialization

Ananyev, Konstantin konstantin.ananyev at intel.com
Wed Feb 19 18:51:41 CET 2014

Hi Thomas,
I am afraid I couldn't send you an url we are using.
We take it from internal Intel ND repository.
Though I think, that latest available to download from Intel ixgbe driver for FreeBSD should have pretty close codebase. 
As a rule of thumb in our internal policy: we take shared code from ND and treat it as read-only (the only exception: ixgbe/ixgbe_osdep.h).
Otherwise it might  become quite messy pretty quickly.
To overcome some problems or shortcomings in ND code people usually use wrappers at the upper layer - that way  was implemented bypass support, loopback support, plus some other fixes (reported number of queues per  VF, etc).
I wonder couldn't your fix also be pushed to the upper layer (in ixgbe_ethdev.c or something)?

-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] 
Sent: Wednesday, February 19, 2014 4:52 PM
To: Ananyev, Konstantin
Cc: Didier Pallard; dev at dpdk.org
Subject: Re: [dpdk-dev] [RFC PATCH 2/2] ixgbe: release software locked semaphores on initialization

19/02/2014 13:41, Ananyev, Konstantin:
> Can the patch be reworked to keep changes under librte_pmd_ixgbe/ixgbe 
> directory untouched? Those files are derived directly from the BSD 
> driver baseline, and any changes will make future merges of newer code 
> more challenging. The changes should be limited to files in the 
> librte_pmd_ixgbe directory (and ethdev). Thanks

Please, could you send an url to the BSD driver baseline ?
By the way, git is very good at rebasing such patches.
And if the fix is good, it should be applied on the baseline.
Refusing a fix without alternative is not an option.

Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

More information about the dev mailing list