H
Henry Markov
My target has an Intel gigabit NIC (Pro 1000) but the SP1 distribution does not
have a driver for it therefore I have been using CD to configure my own driver
component. This has worked for default configurations however I now need to
tune my driver for high speed UDP. I've found that some of the critical tuning
parameters deal with issues such as interrupt moderation and number of receive
descriptors allocated to the driver. For disk based Windows the program ProSet
can be used to configure some of these parameters (there appears to be more
flexibility and more tuning options for the Linux driver). Presumably ProSet
sets registry values however when I use regedit and search for keys such as
"e1000" I can't find anything that I can correlate to the settings I configure
with ProSet.
Is there a systematic method for examining an XP Pro driver such as the one for
the Intel Pro 1000 and determining what registry values are manipulated by its
installer and/or configuration program so that the same registry values can be
identified and set appropriately in XP Embedded?
Henry
have a driver for it therefore I have been using CD to configure my own driver
component. This has worked for default configurations however I now need to
tune my driver for high speed UDP. I've found that some of the critical tuning
parameters deal with issues such as interrupt moderation and number of receive
descriptors allocated to the driver. For disk based Windows the program ProSet
can be used to configure some of these parameters (there appears to be more
flexibility and more tuning options for the Linux driver). Presumably ProSet
sets registry values however when I use regedit and search for keys such as
"e1000" I can't find anything that I can correlate to the settings I configure
with ProSet.
Is there a systematic method for examining an XP Pro driver such as the one for
the Intel Pro 1000 and determining what registry values are manipulated by its
installer and/or configuration program so that the same registry values can be
identified and set appropriately in XP Embedded?
Henry