Bug #588
closed
em(4) Rx and Tx descriptors
0%
Description
There is a way to change the numbers of Rx and Tx descriptors via tunables,
but there isn't any feedback whether it succeeded or not. IMHO it would
be nice to export these values into sysctl as read-only nodes.
regards,
Files
Updated by sepherosa about 17 years ago
There is feedback in the dmesg, if number of RX/TX desc is tuned to a
wrong value. Does it fit your needs?
Best Regards,
sephe
Updated by hasso about 17 years ago
Not wrong, but corrected according to hardware capabilities ;). But you have
to know the code to have this knowledge.
And even in this case if there is silence in dmesg regarding Rx and Tx
descriptors, success isn't the only option. You might make typo while
editing loader.conf for example.
regards,
Updated by dillon about 17 years ago
:Not wrong, but corrected according to hardware capabilities ;). But you have
:to know the code to have this knowledge.
:
:And even in this case if there is silence in dmesg regarding Rx and Tx
:descriptors, success isn't the only option. You might make typo while
:editing loader.conf for example.
:
:regards,
:
:--
:Hasso Tepper
Was there a resolution to this? Do we want to still add the additional
verbosity as per the patch or would it be easier to just change the
device printf to be a little more verbose ?-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by sepherosa about 17 years ago
I have no objection to add two read only sysctl nodes; It may be
better than parsing dmesg if certain program needs those values. If
Matt thinks it is OK too, I will commit it.
Best Regards,
sephe
Updated by dillon about 17 years ago
:I have no objection to add two read only sysctl nodes; It may be
:better than parsing dmesg if certain program needs those values. If
:Matt thinks it is OK too, I will commit it.
:
:Best Regards,
:sephe
I think its probably a bit bloated, but even so it IS a reasonable
solution and we need to move on, so please go ahead and commit it.-Matt
Matthew Dillon
<dillon@backplane.com>