search for: iodelay

...ing idle periods is constantly (every minute) writing to HDD (maybe doing some journaling?) what causes the HDD to constantly spin and never standby: root at rpi:~# pidstat -dl 20 Linux 4.4.50-v7+ (localhost) 11/07/2018 _armv7l_ (4 CPU) 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command 04:10:28 AM 0 832 0.00 0.20 0.20 0 /usr/sbin/smbd -D 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command 04:11:28 AM 0 832 0.00 0.20 0.20 0 /usr/sbin/smbd -D 04:12:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr...

...o HDD >> (maybe doing some journaling?) what causes the HDD to constantly spin >> and never standby: >> >> root at rpi:~# pidstat -dl 20 >> Linux 4.4.50-v7+ (localhost) 11/07/2018 >> _armv7l_ (4 CPU) >> 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command >> 04:10:28 AM 0 832 0.00 0.20 0.20 >> 0 /usr/sbin/smbd -D >> 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command >> 04:11:28 AM 0 832 0.00 0.20 0.20 >> 0 /usr/sbin/smbd -D >> 04:12:08 AM UI...

...t; > (maybe doing some journaling?) what causes the HDD to constantly spin > > and never standby: > > > > root at rpi:~# pidstat -dl 20 > > Linux 4.4.50-v7+ (localhost) 11/07/2018 > > _armv7l_ (4 CPU) > > 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command > > 04:10:28 AM 0 832 0.00 0.20 0.20 > > 0 /usr/sbin/smbd -D > > 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command > > 04:11:28 AM 0 832 0.00 0.20 0.20 > > 0 /usr/sbin/smbd -D > > 04:12:08 A...

...o constantly > > > > spin and never standby: > > > > > > > > root at rpi:~# pidstat -dl 20 > > > > Linux 4.4.50-v7+ (localhost) 11/07/2018 > > > > _armv7l_ (4 CPU) > > > > 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > > > > Command 04:10:28 AM 0 832 0.00 0.20 0.20 > > > > 0 /usr/sbin/smbd -D > > > > 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > > > > Command 04:11:28 AM 0 832 0.00 0.20 0.20 > > >...

...ly (every minute) writing to HDD > (maybe doing some journaling?) what causes the HDD to constantly spin > and never standby: > > root at rpi:~# pidstat -dl 20 > Linux 4.4.50-v7+ (localhost) 11/07/2018 > _armv7l_ (4 CPU) > 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command > 04:10:28 AM 0 832 0.00 0.20 0.20 > 0 /usr/sbin/smbd -D > 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command > 04:11:28 AM 0 832 0.00 0.20 0.20 > 0 /usr/sbin/smbd -D > 04:12:08 AM UID PID kB_rd/s kB_wr...

...me journaling?) what causes the HDD to constantly > >> spin and never standby: > >> > >> root at rpi:~# pidstat -dl 20 > >> Linux 4.4.50-v7+ (localhost) 11/07/2018 > >> _armv7l_ (4 CPU) > >> 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > >> Command 04:10:28 AM 0 832 0.00 0.20 0.20 > >> 0 /usr/sbin/smbd -D > >> 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > >> Command 04:11:28 AM 0 832 0.00 0.20 0.20 > >> 0 /usr/sbin/smbd -D &g...

...at causes the HDD to constantly >>>> spin and never standby: >>>> >>>> root at rpi:~# pidstat -dl 20 >>>> Linux 4.4.50-v7+ (localhost) 11/07/2018 >>>> _armv7l_ (4 CPU) >>>> 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay >>>> Command 04:10:28 AM 0 832 0.00 0.20 0.20 >>>> 0 /usr/sbin/smbd -D >>>> 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay >>>> Command 04:11:28 AM 0 832 0.00 0.20 0.20 >>>> 0 /usr/s...

...naling?) what causes the HDD to constantly > > > spin and never standby: > > > > > > root at rpi:~# pidstat -dl 20 > > > Linux 4.4.50-v7+ (localhost) 11/07/2018 > > > _armv7l_ (4 CPU) > > > 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > > > Command 04:10:28 AM 0 832 0.00 0.20 0.20 > > > 0 /usr/sbin/smbd -D > > > 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > > > Command 04:11:28 AM 0 832 0.00 0.20 0.20 > > > 0 /usr/sbin/smbd -...

...y > >>>> spin and never standby: > >>>> > >>>> root at rpi:~# pidstat -dl 20 > >>>> Linux 4.4.50-v7+ (localhost) 11/07/2018 > >>>> _armv7l_ (4 CPU) > >>>> 04:10:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > >>>> Command 04:10:28 AM 0 832 0.00 0.20 0.20 > >>>> 0 /usr/sbin/smbd -D > >>>> 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > >>>> Command 04:11:28 AM 0 832 0.00 0.20 0.20 > &...

for s10u2, documentation recommends 3 to 9 devices in raidz. what is the basis for this recommendation? i assume it is performance and not failure resilience, but i am just guessing... [i know, recommendation was intended for people who know their raid cold, so it needed no further explanation] thanks... oz -- ozan s. yigit | oz at somanetworks.com | 416 977 1414 x 1540 I have a hard time

...> > Yes, but it isn't doing a read, it is trying to do a write and then > > being cancelled. > > Rowland, > > Can you point us as the evidence that leads you to that conclusion?  OK, the OP posted lines like these: 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command 04:11:28 AM 0 832 0.00 0.20 0.20 0 /usr/sbin/smbd -D And from 'man pidstat' kB_rd/s Number of kilobytes the task has caused to be read from disk per second. kB_wr/s Number of kilobytes the task has caused, or shall cause to be written to d...

This is the start of a paravirt_ops implementation for KVM. Most of it was done by Ingo Molnar, I just moved things around a bit. I don't think there's a measurable performance benefit just yet but there are a few more optimizations that I think we can get in time for 2.6.23 that will be measurable. Regards, Anthony Liguori

This is the start of a paravirt_ops implementation for KVM. Most of it was done by Ingo Molnar, I just moved things around a bit. I don't think there's a measurable performance benefit just yet but there are a few more optimizations that I think we can get in time for 2.6.23 that will be measurable. Regards, Anthony Liguori

...it is trying to do a write and then > > > being cancelled. > > > > Rowland, > > > > Can you point us as the evidence that leads you to that conclusion? > > OK, the OP posted lines like these: > > 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command > 04:11:28 AM 0 832 0.00 0.20 0.20 0 /usr/sbin/smbd -D > > And from 'man pidstat' > > kB_rd/s > Number of kilobytes the task has caused to be read from disk per second. > > kB_wr/s > Number of kilobytes the task...

...+} + static inline int __init check_vmi_rom(struct vrom_header *rom) { struct pci_header *pci; @@ -769,7 +790,7 @@ static inline int __init activate_vmi(vo para_wrap(load_esp0, vmi_load_esp0, set_kernel_stack, UpdateKernelStack); para_fill(set_iopl_mask, SetIOPLMask); para_fill(io_delay, IODelay); - para_fill(set_lazy_mode, SetLazyMode); + para_wrap(set_lazy_mode, vmi_set_lazy_mode, set_lazy_mode, SetLazyMode); /* user and kernel flush are just handled with different flags to FlushTLB */ para_wrap(flush_tlb_user, vmi_flush_tlb_user, flush_tlb, FlushTLB);

...+} + static inline int __init check_vmi_rom(struct vrom_header *rom) { struct pci_header *pci; @@ -769,7 +790,7 @@ static inline int __init activate_vmi(vo para_wrap(load_esp0, vmi_load_esp0, set_kernel_stack, UpdateKernelStack); para_fill(set_iopl_mask, SetIOPLMask); para_fill(io_delay, IODelay); - para_fill(set_lazy_mode, SetLazyMode); + para_wrap(set_lazy_mode, vmi_set_lazy_mode, set_lazy_mode, SetLazyMode); /* user and kernel flush are just handled with different flags to FlushTLB */ para_wrap(flush_tlb_user, vmi_flush_tlb_user, flush_tlb, FlushTLB);

...\ + VDEF(OUTB) \ + VDEF(OUTW) \ + VDEF(OUTS) \ + VDEF(OUTSB) \ + VDEF(OUTSW) \ + VDEF(SetIOPLMask) \ + VDEF(DeactivatePxELongAtomic) \ + VDEF(TestAndSetPxELongBit) \ + VDEF(TestAndClearPxELongBit) \ + VDEF(SetInitialAPState) \ + VDEF(APICWrite) \ + VDEF(APICRead) \ + VDEF(IODelay) \ + VDEF(GetCycleFrequency) \ + VDEF(GetCycleCounter) \ + VDEF(SetAlarm) \ + VDEF(CancelAlarm) \ + VDEF(GetWallclockTime) \ + VDEF(WallclockUpdated)

...\ + VDEF(OUTB) \ + VDEF(OUTW) \ + VDEF(OUTS) \ + VDEF(OUTSB) \ + VDEF(OUTSW) \ + VDEF(SetIOPLMask) \ + VDEF(DeactivatePxELongAtomic) \ + VDEF(TestAndSetPxELongBit) \ + VDEF(TestAndClearPxELongBit) \ + VDEF(SetInitialAPState) \ + VDEF(APICWrite) \ + VDEF(APICRead) \ + VDEF(IODelay) \ + VDEF(GetCycleFrequency) \ + VDEF(GetCycleCounter) \ + VDEF(SetAlarm) \ + VDEF(CancelAlarm) \ + VDEF(GetWallclockTime) \ + VDEF(WallclockUpdated)

...ng cancelled. > > > > > > Rowland, > > > > > > Can you point us as the evidence that leads you to that > > > conclusion? > > > > OK, the OP posted lines like these: > > > > 04:11:08 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay > > Command 04:11:28 AM 0 832 0.00 0.20 0.20 > > 0 /usr/sbin/smbd -D > > > > And from 'man pidstat' > > > > kB_rd/s > > Number of kilobytes the task has caused to be read from disk > > per second. > > >...

On Wed, 7 Nov 2018 15:57:04 -0800 Jeremy Allison via samba <samba at lists.samba.org> wrote: > On Thu, Nov 08, 2018 at 02:34:50AM +0300, Albert Berger via samba > wrote: > > On Thu, Nov 08, 2018 at 06:12:40AM +1300, Andrew Bartlett wrote: > > > On Wed, 2018-11-07 at 15:19 +0300, Albert Berger via samba wrote: > > > >  > > > > I tried in sequence