cvs commit: src/sys/dev/bce if_bce.c src/sys/dev/em
if_em.c if_em.h src/sys/dev/mpt mpt.h mpt_pci.c
Scott Long
scottl at samsco.org
Fri Nov 17 10:13:26 PST 2006
Mark Atkinson wrote:
> (moving to current to avoid dirtying src further)
>
> John Baldwin wrote:
>> jhb 2006-11-15 20:04:57 UTC
>>
>> FreeBSD src repository
>>
>> Modified files:
>> sys/dev/bce if_bce.c
>> sys/dev/em if_em.c if_em.h
>> sys/dev/mpt mpt.h mpt_pci.c
>> Log:
>> Add MSI support to em(4), bce(4), and mpt(4). For now, we only support
>> devices that support a maximum of 1 message, and we use that 1 message
>> instead of the INTx rid 0 IRQ with the same interrupt handler, etc.
>>
>> Revision Changes Path
>> 1.19 +11 -3 src/sys/dev/bce/if_bce.c
>> 1.164 +11 -2 src/sys/dev/em/if_em.c
>> 1.56 +1 -0 src/sys/dev/em/if_em.h
>> 1.31 +1 -0 src/sys/dev/mpt/mpt.h
>> 1.39 +14 -1 src/sys/dev/mpt/mpt_pci.c
>> _______________________________________________
>> cvs-src at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/cvs-src
>> To unsubscribe, send any mail to "cvs-src-unsubscribe at freebsd.org"
>
> This is great, I don't know if you plan on adding MSI support to all network
> drivers that could support it, but here's the output from the Tyan S2895
> (k8WE) for the nve0 and nve1 devices, which report supporting 2 messages.
>
The challenge is knowing what meaning the chip assigns to each of those
messages, as well as knowing what errata come with it. It's not just a
mechanical code change to the driver. You could always try the simple
route with only allocating a single message, but you'd then have to make
sure that it actually works reliably for everyone.
Scott
More information about the freebsd-current
mailing list