.@kernel.org; openocd-devel-
> ow...@lists.sourceforge.net; linux-...@vger.kernel.org;
> da...@davemloft.net; mche...@kernel.org; Linus Torvalds
> <torva...@linux-foundation.org>
> Subject: [patch v16 1/4] Linux 4.15-rc6
>
> From: Linus Torvalds <torva...@linux-foundation.org>
>
.@lists.sourceforge.net; linux-...@vger.kernel.org;
> da...@davemloft.net; mche...@kernel.org; Linus Torvalds
>
> Subject: [patch v16 1/4] Linux 4.15-rc6
>
> From: Linus Torvalds
>
> ---
> Makefile |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> d
From: Linus Torvalds
---
Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index 92b74bc..eb1f597 100644
--- a/Makefile
+++ b/Makefile
@@ -2,7 +2,7 @@
VERSION = 4
PATCHLEVEL = 15
SUBLEVEL = 0
-EXTRAVERSION =
From: Linus Torvalds
---
Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index 92b74bc..eb1f597 100644
--- a/Makefile
+++ b/Makefile
@@ -2,7 +2,7 @@
VERSION = 4
PATCHLEVEL = 15
SUBLEVEL = 0
-EXTRAVERSION = -rc5
+EXTRAVERSION = -rc6
NAME
On Thu, Jan 04, 2018 at 11:27:04AM +0100, Willy Tarreau wrote:
> > The post linked above has numbers with nopcid disabling pcid use, and
> > indeed, the difference is quite measurable.
>
> I'm going to re-run the tests on an Atom C2518 now, which doesn't have pcid,
> I don't even know if it's
On Thu, Jan 04, 2018 at 11:27:04AM +0100, Willy Tarreau wrote:
> > The post linked above has numbers with nopcid disabling pcid use, and
> > indeed, the difference is quite measurable.
>
> I'm going to re-run the tests on an Atom C2518 now, which doesn't have pcid,
> I don't even know if it's
On Wed, Jan 03, 2018 at 01:20:00PM -0800, Andres Freund wrote:
> On 2018-01-03 13:57:25 +0100, Willy Tarreau wrote:
> > I think we should start to think about an option to
> > disable this per process. We could imagine for example a prctl()
> > requiring CAP_SYS_ADMIN to disable it. This would at
On Wed, Jan 03, 2018 at 01:20:00PM -0800, Andres Freund wrote:
> On 2018-01-03 13:57:25 +0100, Willy Tarreau wrote:
> > I think we should start to think about an option to
> > disable this per process. We could imagine for example a prctl()
> > requiring CAP_SYS_ADMIN to disable it. This would at
On 2018-01-03 13:57:25 +0100, Willy Tarreau wrote:
> On Tue, Jan 02, 2018 at 01:09:13PM -0800, Linus Torvalds wrote:
> > On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
> > >
> > > I thought it'd be interesting to run a short benchmark to be able to
> > > estimate the
On 2018-01-03 13:57:25 +0100, Willy Tarreau wrote:
> On Tue, Jan 02, 2018 at 01:09:13PM -0800, Linus Torvalds wrote:
> > On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
> > >
> > > I thought it'd be interesting to run a short benchmark to be able to
> > > estimate the impact of the PTI work
On Tue, Jan 02, 2018 at 01:09:13PM -0800, Linus Torvalds wrote:
> On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
> >
> > I thought it'd be interesting to run a short benchmark to be able to
> > estimate the impact of the PTI work on postgres workloads (which I work
> >
On Tue, Jan 02, 2018 at 01:09:13PM -0800, Linus Torvalds wrote:
> On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
> >
> > I thought it'd be interesting to run a short benchmark to be able to
> > estimate the impact of the PTI work on postgres workloads (which I work
> > on). On my skylake
On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
>
> I thought it'd be interesting to run a short benchmark to be able to
> estimate the impact of the PTI work on postgres workloads (which I work
> on). On my skylake laptop, a memory resident, OLTP workload with 16
>
On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote:
>
> I thought it'd be interesting to run a short benchmark to be able to
> estimate the impact of the PTI work on postgres workloads (which I work
> on). On my skylake laptop, a memory resident, OLTP workload with 16
> connections results in:
On 2017-12-31 14:57:51 -0800, Linus Torvalds wrote:
> With all the x86 pti work coming in late in the rc like this, I'm by
> now almost guaranteed to do an rc8 this release, not because there are
> any known problems, but simply because of the timing of the patches.
>
> Go forth and test,
I
On 2017-12-31 14:57:51 -0800, Linus Torvalds wrote:
> With all the x86 pti work coming in late in the rc like this, I'm by
> now almost guaranteed to do an rc8 this release, not because there are
> any known problems, but simply because of the timing of the patches.
>
> Go forth and test,
I
o far
ASoC: rsnd: fixup ADG register mask
Linus Torvalds (4):
n_tty: fix EXTPROC vs ICANON interaction with TIOCINQ (aka FIONREAD)
x86-32: Fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)
kbuild: add '-fno-stack-check' to kernel build options
Linux 4.15-rc6
o far
ASoC: rsnd: fixup ADG register mask
Linus Torvalds (4):
n_tty: fix EXTPROC vs ICANON interaction with TIOCINQ (aka FIONREAD)
x86-32: Fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)
kbuild: add '-fno-stack-check' to kernel build options
Linux 4.15-rc6
18 matches
Mail list logo