On Fri, 15 Sep 2017, Scott Long wrote:
On Sep 13, 2017, at 9:12 AM, Sean Bruno <sbr...@freebsd.org> wrote:
#blamebruno
A large burden.
Reviewed by: sbruno
Approved by: sbruno (mentor)
Sponsored by: Limelight Networks
Differential Revision: https://reviews.freebsd.org/D12235
*gasps at the LoC count and number of changed drivers*
Could someone please better break this up in the future..?
This ridiculous loc was due to the amount of restructuring needed to get
us back to being in sync with our development. The future will not have
this big of a commit/change and should be more bite/fun sized.
The #blamebruno tag in the commit log was to indicate that this was not
something Stephen was doing on his own, but was something that I had
induced over the last few months during testing.
This breaks my system. I prior to this commit, I had igb0 and igb1. Now I
only have igb0, and it\xe2]x80\x99s like igb1 isn\xe2\x80\x99tt even trying to
attach. Unfortunately,
this breaks my nfsroot setup, so I need to roll back my tree. Please let me
know if there\xe2\x80\x99ss anything I can provide to help debugging.
It gives lesser breakage here:
- with an old PCI em, an error that occur every few makeworlds over nfs now
hang the hardware. It used to be recovered from afger about 10 seconds.
This only happened once. I then applied my old fix which ignores the
error better so as to recover from it immediately. This seems to work as
before.
- with a newer PCI-e em, throughput as measured by netblast is down by
more that a factor of 2 since last month.
Bruce
_______________________________________________
svn-src-head@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
