Re: MFC of em/igb drivers
- From: "Jack Vogel" <jfvogel@xxxxxxxxx>
- Date: Sat, 3 May 2008 13:39:31 -0700
On Sat, May 3, 2008 at 10:24 AM, Scott Long <scottl@xxxxxxxxxx> wrote:
Jack Vogel wrote:
On Sat, May 3, 2008 at 4:45 AM, Kostik Belousov <kostikbel@xxxxxxxxx>wrote:
On Sat, May 03, 2008 at 12:14:32AM -0700, Jack Vogel wrote:
I got the new drivers in Friday afternoon for those that don't see CVS> messages.
> The igb driver is for 82575 and 82576 adapters, it has multiqueue
get the> MSIX, there will be more server type enhancements in that driver as I
support however> time.
> The em driver now will be client oriented, the latest hardware
dual-port adapter,> is for 82574, Hartwell, which is a really nice low cost PCIE
supports 5> that actually also has MSIX. This first released support for it will
> use 3 interrupt
> vectors, one for TX, one for RX, and Link. The hardware actually
as my> vectors, so I am planning to add support for another RX and TX queue
the driver> schedule allows.
> Hartwell is also the first adapter that has IEEE 1588 PTP support,
on> provides init and an ioctl interface to use that facility, I hope we
> see software
> support follow on soon. This is an early announcement, I am not sure
> exact dates for availability but they should be soon.
> As ever, issues and bugs should be sent to me. Cheers everyone!
Besides the broken tinderbox, you did not connected the igb module to
the module build. Is this intentional ?
No, not intentional, both issues are now fixed, sorry, was tired yesterday
Is it still true that support for the 575 moved from em to igb? If so,
please put an entry in src/UPDATING about it and ask the re/docs team to
make sure it's documented in the next release notes.
Ahhh yes, I forgot about that, will do Scott.
freebsd-net@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: read() returns ETIMEDOUT on steady TCP connection
- Next by Date: Troubles with em on FreeBSD 7
- Previous by thread: Re: MFC of em/igb drivers
- Next by thread: IPPROTO_DIVERT and PF_INET6