similar to: [RESENDx2] [PULL] virtio: fix barriers for virtio-mmio

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

(I called the tag to-linus. I think it worked). To git at github.com:rustyrussell/linux.git + 3ed0016...b6c96c0 master -> master (forced update) + 815645d...f8e8df5 to-linus -> to-linus (forced update) + git request-pull remotes/origin/master git://github.com/rustyrussell/linux.git The following changes since commit e343a895a9f342f239c5e3c5ffc6c0b1707e6244: Merge tag

(I called the tag to-linus. I think it worked). To git at github.com:rustyrussell/linux.git + 3ed0016...b6c96c0 master -> master (forced update) + 815645d...f8e8df5 to-linus -> to-linus (forced update) + git request-pull remotes/origin/master git://github.com/rustyrussell/linux.git The following changes since commit e343a895a9f342f239c5e3c5ffc6c0b1707e6244: Merge tag

From: Mark Brown <broonie at linaro.org> According to the README at the existing URL the spec has moved to github so update the documentation to match. Signed-off-by: Mark Brown <broonie at linaro.org> --- Documentation/devicetree/bindings/virtio/mmio.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/virtio/mmio.txt

From: Mark Brown <broonie at linaro.org> According to the README at the existing URL the spec has moved to github so update the documentation to match. Signed-off-by: Mark Brown <broonie at linaro.org> --- Documentation/devicetree/bindings/virtio/mmio.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/virtio/mmio.txt

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,

On Tue, Nov 01, 2011 at 10:39:08AM +1030, Rusty Russell wrote: > * [new tag] rusty at rustcorp.com.au-v3.1-7196-gac5be1e -> rusty at rustcorp.com.au-v3.1-7196-gac5be1e > > The following changes since commit 839d8810747bbf39e0a5a7f223b67bffa7945f8d: > > Merge branch 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging (2011-10-30

On Tue, Nov 01, 2011 at 10:39:08AM +1030, Rusty Russell wrote: > * [new tag] rusty at rustcorp.com.au-v3.1-7196-gac5be1e -> rusty at rustcorp.com.au-v3.1-7196-gac5be1e > > The following changes since commit 839d8810747bbf39e0a5a7f223b67bffa7945f8d: > > Merge branch 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging (2011-10-30

On Tue, Dec 03, 2013 at 12:40:21PM +0000, Mark Brown wrote: > From: Mark Brown <broonie at linaro.org> > > According to the README at the existing URL the spec has moved to github > so update the documentation to match. > > Signed-off-by: Mark Brown <broonie at linaro.org> Even that's no longer accurate :) There should be a new address RSN, I'll respond.

I use recipient_delimiter addresseses quiet a bit, and I want to put several of them into a mailbox if anyof (header :contains ["to"] [ ?FOO", ?foo", ?bar", ?florin"]) { fileinto :create ?later"; stop; } When I get an email addressed to me+FOO at example.com or me_florin at example.com, the messages end up in my inbox (Yes, I have both + and _

> On 26 Jul 2017, at 7:57 pm, Olaf Hopp <Olaf.Hopp at kit.edu> wrote: > > Dear collegues, > > many thanks for your valuable input. > > Since we are an university GEO-IP blocking is not an option for us. > Somestimes I think it should ;-) > > My "mistake" was that I had just *one* fail2ban filter for both cases: > "wrong password" and

On Thu, May 03, 2018 at 03:30:03PM +0800, Jason Wang wrote: > On 2018?05?03? 10:59, Tiwei Bie wrote: > > This patch introduces the support for VIRTIO_F_IO_BARRIER. > > When this feature is negotiated, driver will use the barriers > > suitable for hardware devices. > > > > Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> > > --- > >

On Thu, May 03, 2018 at 03:30:03PM +0800, Jason Wang wrote: > On 2018?05?03? 10:59, Tiwei Bie wrote: > > This patch introduces the support for VIRTIO_F_IO_BARRIER. > > When this feature is negotiated, driver will use the barriers > > suitable for hardware devices. > > > > Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> > > --- > >

On Thu, May 03, 2018 at 05:09:44PM +0800, Jason Wang wrote: > On 2018?05?03? 16:30, Tiwei Bie wrote: > > On Thu, May 03, 2018 at 03:30:03PM +0800, Jason Wang wrote: > > > On 2018?05?03? 10:59, Tiwei Bie wrote: > > > > This patch introduces the support for VIRTIO_F_IO_BARRIER. > > > > When this feature is negotiated, driver will use the barriers > >

On 2018?05?03? 16:30, Tiwei Bie wrote: > On Thu, May 03, 2018 at 03:30:03PM +0800, Jason Wang wrote: >> On 2018?05?03? 10:59, Tiwei Bie wrote: >>> This patch introduces the support for VIRTIO_F_IO_BARRIER. >>> When this feature is negotiated, driver will use the barriers >>> suitable for hardware devices. >>> >>> Signed-off-by: Tiwei Bie

From the Notes section of my sieve file, because I always forget this # MORE NOTES: # Using :localpart takes just the local part of an address # header selects a header, address selects an address # Looks like this is the spec: # :localpart = :user+:detail # address are :localpart @ :domain, or :user + :detail @ :domain # See RFC5233 I use this bit for figuring out what :detail something (might)

Dear collegues, many thanks for your valuable input. Since we are an university GEO-IP blocking is not an option for us. Somestimes I think it should ;-) My "mistake" was that I had just *one* fail2ban filter for both cases: "wrong password" and "unknown user". Now I have two distinct jails: The first one just for "wrong password" and here the findtime,

On 04/08/2015 01:42 AM, Michael S. Tsirkin wrote: > On Tue, Apr 07, 2015 at 05:47:42PM -0700, Alexander Duyck wrote: >> This change makes it so that instead of using smp_wmb/rmb which varies >> depending on the kernel configuration we can can use dma_wmb/rmb which for >> most architectures should be equal to or slightly more strict than >> smp_wmb/rmb. >> >>

On 04/08/2015 01:42 AM, Michael S. Tsirkin wrote: > On Tue, Apr 07, 2015 at 05:47:42PM -0700, Alexander Duyck wrote: >> This change makes it so that instead of using smp_wmb/rmb which varies >> depending on the kernel configuration we can can use dma_wmb/rmb which for >> most architectures should be equal to or slightly more strict than >> smp_wmb/rmb. >> >>