Re: kern.sched.quantum: Creepy, sadistic scheduler

Eugene Grosbein wrote: I see no reasons to use SHED_ULE for such single core systems and use SCHED_BSD. Nitpicking: it is not a single core system, it's a dual that for now is equipped with only one chip, the other is in the shelf. But seriously, I am currently working myself through the

Re: Problems with ifconfig when starting all jails after 10.3 -> 10.4 upgrade

On 2018-04-05 10:28 AM, Marc Branchaud wrote: Hi all, I just upgraded from 10.3 to 10.4, and "/etc/rc.d/jail start" is having problems starting all of my jails: # /etc/rc.d/jail start Starting jails:xipbuild_3_3: created ifconfig:: bad value jail: xipbuild_3_3_8: /sbin/ifconfig lo1 inet

Re: [Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

On Fri, 2018-04-06 at 13:09 +, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323 > > Bug ID: 227323 >    Summary: [patch] [spi] sys/modules/spi/mx25l cannot be > built > outside of kernel build environment >  

[Bug 227322] [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227322 Ian Lepore changed: What|Removed |Added Resolution|--- |FIXED

[Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323 Ian Lepore changed: What|Removed |Added Resolution|--- |FIXED

[Bug 227322] [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227322 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: ian Date: Fri Apr 6 16:48:08 UTC 2018 New revision: 332113 URL: https://svnweb.freebsd.org/changeset/base/332113 Log: MFC r331868: Add

[Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: ian Date: Fri Apr 6 16:48:08 UTC 2018 New revision: 332113 URL: https://svnweb.freebsd.org/changeset/base/332113 Log: MFC r331868: Add

libmap non-absolute paths broken in 11.1-STABLE

Hi! I've just updated my desktop from early 11.1-STABLE to recent one 11.1-STABLE and found that non-absolute paths do not work anymore, like this: libevent-2.0.so.5 compat/pkg/libevent-2.0.so.5.1.10 With luck, this still works: libevent-2.0.so.5

Re: TRIM, iSCSI and %busy waves

On Fri, Apr 6, 2018 at 2:56 AM, Borja Marcos wrote: > > > On 6 Apr 2018, at 10:41, Steven Hartland wrote: > > That is very hw and use case dependent. > > The reason we originally sponsored the project to add TRIM to ZFS was that > in our case without

Re: TRIM, iSCSI and %busy waves

On Fri, Apr 6, 2018 at 1:58 AM, Borja Marcos wrote: > > > On 5 Apr 2018, at 17:00, Warner Losh wrote: > > > > I'm working on trim shaping in -current right now. It's focused on NVMe, > > but since I'm doing the bulk of it in cam_iosched.c, it will eventually

[Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323 Bug ID: 227323 Summary: [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment Product: Base System Version: 11.1-STABLE Hardware:

[Bug 227322] [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227322 Bug ID: 227322 Summary: [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment Product: Base System Version: 11.1-STABLE

Re: TRIM, iSCSI and %busy waves

> On 6 Apr 2018, at 10:56, Borja Marcos wrote: > > P.S: Attaching the graphs that were lost. And, silly me, repeating the same mistakes over and over. http://frobula.crabdance.com:8001/publicfiles/OneBonnie.png

Re: TRIM, iSCSI and %busy waves

> On 6 Apr 2018, at 10:41, Steven Hartland wrote: > > That is very hw and use case dependent. > > The reason we originally sponsored the project to add TRIM to ZFS was that in > our case without TRIM the performance got so bad that we had to secure erase > disks

Re: TRIM, iSCSI and %busy waves

That is very hw and use case dependent. The reason we originally sponsored the project to add TRIM to ZFS was that in our case without TRIM the performance got so bad that we had to secure erase disks every couple of weeks as they simply became so slow they where unusable. Now admittedly that

Re:Response

Hello, Please, Let me know if you received my message, I have sent more than 3 messages to you in the last 3 months without response,get back to me Yours, Veronica Garcia ___ freebsd-stable@freebsd.org mailing list

Re: TRIM, iSCSI and %busy waves

> On 5 Apr 2018, at 17:00, Warner Losh wrote: > > I'm working on trim shaping in -current right now. It's focused on NVMe, > but since I'm doing the bulk of it in cam_iosched.c, it will eventually be > available for ada and da. The notion is to measure how long the TRIMs take,