Re: Sluggish performance on head r311648

> One thing I keep a look out for, is in gstat, if one drive is busier > than the others, it's a clear sign of a drive dying. Offlining and > replacing the drive usually makes a huge difference. > Also, in all of these cases, SMART data shows no sign of problem and no > errors in 'zpool status'. J

Re: Sluggish performance on head r311648

On 11/01/2017 15:32, Ultima wrote: I'v been noticing lately sluggish performance, maybe zfs? First noticed this a few days ago right after upgrading on Jan 7th to r311648 and the last upgrade before that was around dec 30-jan 1 (not sure of rev). Decided to upgrade again today. I usually build an

Wayland update

Howdy It's time for another update from your friendly neighborhood graphics programmer. I will be keeping a live document with instructions etc here https://github.com/johalun/documentation/blob/master/wayland.md Please visit any time for information about Wayland on FreeBSD. Suggestions for im

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

> A flame graph for the core cycle count and a flame graph with cache miss > stats from pmc would be a great start. > > > ​I didn't know the exact event name to use for cache miss stats, but here > are the flame graphs for CPU_CLK_UNHALTED_CORE: > http://dev.bsdrp.net/netgate.r311848.C

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On 01/11/17 15:44, Sean Bruno wrote: > >> My tunning are (same for both test): >> hw.igb.rxd="2048" (it should be useless now) >> hw.igb.txd="2048" (it should be useless now) >> hw.em.rxd="2048" >> hw.em.txd="2048" >> hw.igb.rx_process_limit="-1" (It should be useless now too) >> hw.em.rx_proces

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

> My tunning are (same for both test): > hw.igb.rxd="2048" (it should be useless now) > hw.igb.txd="2048" (it should be useless now) > hw.em.rxd="2048" > hw.em.txd="2048" > hw.igb.rx_process_limit="-1" (It should be useless now too) > hw.em.rx_process_limit="-1" > > dev.igb.2.fc=0 > dev.igb.3.fc=

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On Wed, Jan 11, 2017 at 9:40 PM, Matthew Macy wrote: > > > > I can generate profiling data for you: what kind of data do you want > ? > > > > > > > A flame graph for the core cycle count and a flame graph with cache miss > stats from pmc would be a great start. > > ​I didn't know the exact e

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

> > > My tunning are (same for both test): > > > hw.igb.rxd="2048" (it should be useless now) > > > hw.igb.txd="2048" (it should be useless now) > > Matt: I think he meant "useless now" because there is no igb, and the > below hw.em version covers it. No. igb still exists and the old t

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On 2017-01-11 15:37, Matthew Macy wrote: > You can still explicitly set the number of descriptors. It is now reported > under the dev sysctl tree. dev... > > -M > > > On Wed, 11 Jan 2017 12:34:23 -0800 Olivier Cochard-Labbé > wrote > > > > On Wed, Jan 11, 2017 at 9:13 PM, Matth

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On Wed, Jan 11, 2017 at 9:13 PM, Matthew Macy wrote: > > > Hmmm ... did your old tests do 4 or 8 queues on this hardware? > > > > Did the old tests run 1024 tx/rx slots or the max 4096? > > That's a great point, only having one thread per core could easily account > for this. I'm hoping Sean c

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

> > I can generate profiling data for you: what kind of data do you want ? > > > A flame graph for the core cycle count and a flame graph with cache miss stats from pmc would be a great start. ___ freebsd-current@freebsd.org mailing list http

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

You can still explicitly set the number of descriptors. It is now reported under the dev sysctl tree. dev... -M On Wed, 11 Jan 2017 12:34:23 -0800 Olivier Cochard-Labbé wrote > > On Wed, Jan 11, 2017 at 9:13 PM, Matthew Macy wrote: > > > Hmmm ... did your old tests do 4 o

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On Wed, 11 Jan 2017 12:02:06 -0800 Sean Bruno wrote > > > On 01/11/17 12:47, Olivier Cochard-Labbé wrote: > > On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno > > wrote: > > > > > > > > Olivier: > > > > Give this a quick try.

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On 01/11/17 12:47, Olivier Cochard-Labbé wrote: > On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno > wrote: > > > > Olivier: > > Give this a quick try. This isn't the correct way to do this, but I > want to see if I'm on the right path: > > > ​thanks, it

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno wrote: > > > Olivier: > > Give this a quick try. This isn't the correct way to do this, but I > want to see if I'm on the right path: > ​thanks, it fix the problem, I've got back the 4 queues:​ ​igb2: port 0x3000-0x301f mem 0xdfea-0xdfeb,0xd

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

> > x head r311848: packets per second > + head r311849 and BAR patch: packets per second > +--+ > |++++ + xxx x x| > |

Re: evdev no /dev/input FreeBSD 12.0-CURRENT #0 r311461

Jesper Schmitz Mouridsen (jesper@schmitz.computer) wrote: > Hello. > > I'm new to using current and to posting here. > I've a old spare T60 1951-FEG wiith Intel Graphics Media Accelerator 950 > (info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0). > Intel Core 2 Duo (Merom) T5600.

evdev no /dev/input FreeBSD 12.0-CURRENT #0 r311461

Hello. I'm new to using current and to posting here. I've a old spare T60 1951-FEG wiith Intel Graphics Media Accelerator 950 (info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0). Intel Core 2 Duo (Merom) T5600. My goal is to try out weston /wayland from xserver-mesa-next-udev [

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On 01/11/17 05:54, Matthew Macy wrote: > > > > On Wed, 11 Jan 2017 01:23:46 -0800 Olivier Cochard-Labbé > wrote > > On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wrote: > > > > > > > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > > > IFLIB in the

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On Wed, 11 Jan 2017 01:23:46 -0800 Olivier Cochard-Labbé wrote > On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wrote: > > > > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > > IFLIB in the kernel. > > > > At this point, the driver deviates from Int

Re: CURRENT: em0 NIC freezes under heavy I/O on net

On Wed, 11 Jan 2017 03:06:19 -0800 Matthew Macy wrote: Hello, thanks for your responding. Your Email looks funny in my claws-mail ;-) You asked whether it started with the introduction of IFLIB - I do not know. Last week (I think it was Friday, and I did at least two updates of world/kernel th

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wrote: > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > IFLIB in the kernel. > > At this point, the driver deviates from Intel's code dramatically and > you now get to yell directly into the freebsd-net@ megaphone for things

Re: Sluggish performance on head r311648

On Wed, 2017-01-11 at 00:02 -0500, Ultima wrote: > I'v been noticing lately sluggish performance, maybe zfs? First > noticed > this a few days ago right after upgrading on Jan 7th to r311648 and > the > last upgrade before that was around dec 30-jan 1 (not sure of rev). > Decided > to upgrade again

FreeBSD_HEAD_i386 - Build #4628 - Fixed

FreeBSD_HEAD_i386 - Build #4628 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4628/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4628/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4628/console Change summaries: 311

Re: CURRENT: em0 NIC freezes under heavy I/O on net

Sorry, I meant to send that to the other thread. Was this after the iflib driver commit? If so it's odd that we haven't seen anything like this and I'll try to get a fix in ASAP. On Wed, 11 Jan 2017 03:06:19 -0800 Me wrote It looks like I have the wrong m

Re: CURRENT: em0 NIC freezes under heavy I/O on net

It looks like I have the wrong msix bar value for your NIC. Will fix in the next day or so.-M On Wed, 11 Jan 2017 00:27:30 -0800 O. Hartmann wrote Running recent CURRENT (FreeBSD 12.0-CURRENT #5 r311919: Wed Jan 11 08:24:28 CET 2017 amd64), the system fr

FreeBSD_HEAD_i386 - Build #4627 - Failure

FreeBSD_HEAD_i386 - Build #4627 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4627/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4627/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/4627/console Change summaries: 3

CURRENT: em0 NIC freezes under heavy I/O on net

Running recent CURRENT (FreeBSD 12.0-CURRENT #5 r311919: Wed Jan 11 08:24:28 CET 2017 amd64), the system freezes when doing a rsync over automounted (autofs) NFSv4 filesystem, mounted from another CURRENT server (same revision, but with BCM NICs). The host in question is a Fujitsu Celsius M740 equ