netdev - Re: ixgbe in kernel driver question

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] [day] [month] [year] [list]

Date:	Thu, 05 Feb 2009 13:53:55 +0100
From:	Paweł Staszewski <pstaszewski@...are.pl>
To:	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
CC:	Linux Network Development list <netdev@...r.kernel.org>
Subject: Re: ixgbe in kernel driver question

Waskiewicz Jr, Peter P pisze:
>> I have question about ixgbe in kernel driver compared to ixgbe driver 
>> that is on sourceforge
>> http://sourceforge.net/project/showfiles.php?group_id=42302&package_id=247088
>>
>> What is difference between this drivers ?
>> and does driver in kernel 2.6.28.2
>>     
>
> These drivers should be relatively kept in sync.  We release our new 
> software to SourceForge first, since that is an on-demand push from Intel.  
> The upstream driver usually has the necessary patches in the queue for the 
> next kernel, but due to hardware release schedules and kernel release 
> schedules not aligning most of the time, there will be differences.
>
> Now these drivers are not intended to be identical.  One main difference, 
> for example, is the upstream driver has no module option support.  The 
> SourceForge driver does support some module options.
>
>   
>> Or this driver have different versions releases ? with different changes 
>> that are made in kernel tree network drivers
>>
>> because i have problems with in kernel ixgbe drivers that i can compare 
>> to some fixes that are made in:
>> 1.3.31.5 driver on e1000 site
>> http://sourceforge.net/project/shownotes.php?release_id=611160&group_id=42302
>>
>> i think about this fix:
>>
>> cpu utilization fix for MSI and legacy interrupts in kernels with CONFIG_NETDEVICES_MULTIQUEUE enabled but default (non multiqueue) aware qdisc loaded
>>     
>
> Yes.  These fixes are already queued or accepted for the next version of 
> the kernel driver.  The bottom line is we, Intel, own the SourceForge 
> driver and its release schedules.  The Linux community ultimately owns the 
> in-kernel driver and those release schedules, so there will almost always 
> be differences.
>
> I hope this helps,
>
> -PJ Waskiewicz
> peter.p.waskiewicz.jr@...el.com
>
>
>   
thanks for reply all is clear now.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html