From: "Paweł Staszewski" <pstaszewski@itcare.pl>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: ixgbe in kernel driver question
Date: Thu, 05 Feb 2009 13:53:55 +0100 [thread overview]
Message-ID: <498AE163.5040905@itcare.pl> (raw)
In-Reply-To: <Pine.WNT.4.64.0902041121030.4348@ppwaskie-MOBL2.amr.corp.intel.com>
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@intel.com
>
>
>
thanks for reply all is clear now.
prev parent reply other threads:[~2009-02-05 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 16:11 ixgbe in kernel driver question Paweł Staszewski
2009-01-30 16:22 ` [ SPAM ] " Paweł Staszewski
2009-02-04 19:28 ` Waskiewicz Jr, Peter P
2009-02-05 12:53 ` Paweł Staszewski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=498AE163.5040905@itcare.pl \
--to=pstaszewski@itcare.pl \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.