search for: harsher

We were cheating with our barriers; using the smp ones rather than the real device ones. That was fine, until virtio-mmio came along, which could be talking to a real device (a non-SMP CPU). Unfortunately, just putting back the real barriers (reverting d57ed95d) causes a performance regression on virtio-pci. In particular, Amos reports netbench's TCP_RR over virtio_net CPU utilization

We were cheating with our barriers; using the smp ones rather than the real device ones. That was fine, until virtio-mmio came along, which could be talking to a real device (a non-SMP CPU). Unfortunately, just putting back the real barriers (reverting d57ed95d) causes a performance regression on virtio-pci. In particular, Amos reports netbench's TCP_RR over virtio_net CPU utilization

Olaf Hopp <Olaf.Hopp at kit.edu> wrote: > And I have a new one just for "unknown user" and here my bantime and findtime > are much bigger and the retries are just '2'. So here I'm much harsher. > I'll keep an eye on my logs and maybe some more twaeking is necessary. Just be careful about typos (like twaeking!): users could simply misspell their username, or get mixed up with some another account or alias. This is why I favour targetting known bad accounts, not merely accounts tha...

...ONFIG_H */ > > Hi: > > I believe this depends on Michael's patch of > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > ? > > Thanks We already have below commit and some other related commits in the tree: 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") They should have already guaranteed that virtio_Xmb() will be OK for hardware devices when vq->weak_barriers is false. If my understanding is correct, the barriers used in this case are overkill. So Michael's patch is to make the barriers weaker (or better). Best...

...ONFIG_H */ > > Hi: > > I believe this depends on Michael's patch of > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > ? > > Thanks We already have below commit and some other related commits in the tree: 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") They should have already guaranteed that virtio_Xmb() will be OK for hardware devices when vq->weak_barriers is false. If my understanding is correct, the barriers used in this case are overkill. So Michael's patch is to make the barriers weaker (or better). Best...

...e commit b3b1b70e62a603f473619dbebc3b3d23f535e6f8: Merge branch 'usb-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb (2011-12-22 12:59:47 -0800) are available in the git repository at: git://github.com/rustyrussell/linux.git master Rusty Russell (1): virtio: harsher barriers for virtio-mmio. drivers/lguest/lguest_device.c | 8 +++++--- drivers/s390/kvm/kvm_virtio.c | 2 +- drivers/virtio/virtio_mmio.c | 7 ++++--- drivers/virtio/virtio_pci.c | 4 ++-- drivers/virtio/virtio_ring.c | 34 +++++++++++++++++++++------------- include/linux/vi...

...e commit b3b1b70e62a603f473619dbebc3b3d23f535e6f8: Merge branch 'usb-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb (2011-12-22 12:59:47 -0800) are available in the git repository at: git://github.com/rustyrussell/linux.git master Rusty Russell (1): virtio: harsher barriers for virtio-mmio. drivers/lguest/lguest_device.c | 8 +++++--- drivers/s390/kvm/kvm_virtio.c | 2 +- drivers/virtio/virtio_mmio.c | 7 ++++--- drivers/virtio/virtio_pci.c | 4 ++-- drivers/virtio/virtio_ring.c | 34 +++++++++++++++++++++------------- include/linux/vi...

...s ["From"] [?kreme.com", ?localdomain1.tld?, "localdomain2.tld", "localdomain3.tld", ?covisp.net? ]){ fileinto :create "priority"; } -- She'd always tried to face towards the light. But the harder you stared into the brightness the harsher it burned into you until, at last, the temptation picked you up and bid you turn around to see how long, rich, strong and dark, streaming away behind you, your shadow had become- --Carpe Jugulum

...t; The first one just for "wrong password" and here the findtime, bantime, retries > are tolerant to typos. > > And I have a new one just for "unknown user" and here my bantime and findtime > are much bigger and the retries are just '2'. So here I'm much harsher. > I'll keep an eye on my logs and maybe some more twaeking is necessary. > > Another interesting observation: > I activated > auth_verbose_passwords = plain > to log the plain password when (and only when) there is "unknown user". > It reveals that all different...

...; > > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > > > > > ? > > > > > > Thanks > > We already have below commit and some other related commits > > in the tree: > > > > 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") > > > > They should have already guaranteed that virtio_Xmb() will > > be OK for hardware devices when vq->weak_barriers is false. > > If my understanding is correct, the barriers used in this > > case are overkill. So Michael's patch...

...al. An animal that is tagged and recaptured 2 days later with a tag and 30 days later without one could have an assumed tag retention of 2 days (minimum confirmed) or 30 days (maximum possible). Both are significant with a survtest, but the K-M plots differ. A plot of minimum confirmed (overall harsher data, lots of 0 days and 1 or 2 days) yields a curve with a steep initial drop in ?survival?, but then a leveling off and straight line thereafter at about 80% survival. Plotting the maximum possible dates (same number of losses/retention, but retention times are longer, the length to the next...

...animal that is tagged and recaptured 2 days later with a tag and 30 days later without one could have an assumed tag retention of 2 days (minimum confirmed) or 30 days (maximum possible). > > Both are significant with a survtest, but the K-M plots differ. A plot of minimum confirmed (overall harsher data, lots of 0 days and 1 or 2 days) yields a curve with a steep initial drop in ?survival?, but then a leveling off and straight line thereafter at about 80% survival. Plotting the maximum possible dates (same number of losses/retention, but retention times are longer, the length to the next capt...

...believe this depends on Michael's patch of >> >> "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" >> >> ? >> >> Thanks > We already have below commit and some other related commits > in the tree: > > 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") > > They should have already guaranteed that virtio_Xmb() will > be OK for hardware devices when vq->weak_barriers is false. > If my understanding is correct, the barriers used in this > case are overkill. So Michael's patch is to make the barriers &...

On Dec 7, 2015 07:45, "Johnny Hughes" <johnny at centos.org> wrote: > > On 12/06/2015 10:11 PM, Greg Lindahl wrote: > > On Sun, Dec 06, 2015 at 09:22:15PM -0500, Jonathan Billings wrote: > >> On Sun, Dec 06, 2015 at 06:35:58PM +0000, Timothy Murphy wrote: > >>> Always Learning wrote: > >>> > >>>> I always admire

...caldomain1.tld?, > "localdomain2.tld", "localdomain3.tld", ?covisp.net? ]){ > fileinto :create "priority"; > } > > > > -- > She'd always tried to face towards the light. But the harder you stared into > the brightness the harsher it burned into you until, at last, the temptation > picked you up and bid you turn around to see how long, rich, strong and dark, > streaming away behind you, your shadow had become- --Carpe Jugulum

I am using asterisk 1.6.0 and -- not all the time -- when a caller comes in and my ivrdials an extension, the ring he gets sounds like a modem handshake instead of the normal ring tone and it only sounds once even if the phone is not picked up. Anyone seeing this -- the logs look fine as far as I can tell. -- Your life is like a penny. You're going to lose it. The question is: How do you

...ve two distinct jails: The first one just for "wrong password" and here the findtime, bantime, retries are tolerant to typos. And I have a new one just for "unknown user" and here my bantime and findtime are much bigger and the retries are just '2'. So here I'm much harsher. I'll keep an eye on my logs and maybe some more twaeking is necessary. Another interesting observation: I activated auth_verbose_passwords = plain to log the plain password when (and only when) there is "unknown user". It reveals that all different IPs trying one unknown account alw...

...e, restore handlers to support S4 Davidlohr Bueso (1): lguest: move the lguest tool to the tools directory Jacek Galowicz (1): lguest: switch segment-voodoo-numbers to readable symbols Michael S. Tsirkin (1): virtio_blk: fix config handler race Rusty Russell (7): virtio: harsher barriers for rpmsg. virtio: document functions better. virtio: rename virtqueue_add_buf_gfp to virtqueue_add_buf virtio: support unlocked queue kick virtio: avoid modulus operation. virtio: expose added descriptors immediately. virtio: add debugging if driver doe...

...e, restore handlers to support S4 Davidlohr Bueso (1): lguest: move the lguest tool to the tools directory Jacek Galowicz (1): lguest: switch segment-voodoo-numbers to readable symbols Michael S. Tsirkin (1): virtio_blk: fix config handler race Rusty Russell (7): virtio: harsher barriers for rpmsg. virtio: document functions better. virtio: rename virtqueue_add_buf_gfp to virtqueue_add_buf virtio: support unlocked queue kick virtio: avoid modulus operation. virtio: expose added descriptors immediately. virtio: add debugging if driver doe...

...; This is what we're dealing with now? > > > > OK. I will recommend we move away from CentOS. > > This seems to be raising what to me is a trivial issue > to an absurd level of hostility. > Johnny Hughes' comment was uncharacteristically harsh; > and yours is even harsher. > > To me, CentOS is a highly stable OS for my home servers, > and I am eternally grateful to Johnny Hughes and his colleagues > for carrying out what looks to me like an impossibly complex task. > > The numbering of packages is a very small part of this. > On the other hand,...