linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Cc: sshegde@linux.ibm.com, npiggin@gmail.com,
	christophe.leroy@csgroup.eu, maddy@linux.ibm.com,
	bigeasy@linutronix.de, ankur.a.arora@oracle.com,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	vschneid@redhat.com, peterz@infradead.org
Subject: [PATCH 0/3] powerpc: Enable dynamic preemption
Date: Mon, 25 Nov 2024 09:52:09 +0530	[thread overview]
Message-ID: <20241125042212.1522315-1-sshegde@linux.ibm.com> (raw)

Once the lazy preemption is supported, it makes sense to enable dynamic
preemption. One can change the preemption model without changing the
kernel. 

Overheads of dynamic preemption seems reasonable for some of the
workloads. Tested with db2 database workload, unixbench, schbench
and hackbench. Except hackbench pipe rest show similar numbers as
without dynamic preemption specially for preempt=none. 

These patches *depend* on lazy preemption patches[1] to be applied
first on tip/sched/core tree. 

The reason for arch/asm/preempt.h is to enable arch specific preempt
enablements. Also, there is plan to move preempt count to paca for 64
bit systems as idea was discussed in [2]

[1] https://lore.kernel.org/all/20241116192306.88217-1-sshegde@linux.ibm.com/#t 
[2] https://lore.kernel.org/all/14d4584d-a087-4674-9e2b-810e96078b3a@linux.ibm.com/ 

Shrikanth Hegde (3):
  powerpc: copy preempt.h into arch/include/asm
  powerpc: support dynamic preemption
  powerpc: print right preemption model in die

 arch/powerpc/Kconfig               |   1 +
 arch/powerpc/include/asm/preempt.h | 101 +++++++++++++++++++++++++++++
 arch/powerpc/kernel/interrupt.c    |   6 +-
 arch/powerpc/kernel/traps.c        |   6 +-
 arch/powerpc/lib/vmx-helper.c      |   2 +-
 5 files changed, 113 insertions(+), 3 deletions(-)
 create mode 100644 arch/powerpc/include/asm/preempt.h

-- 
2.39.3



             reply	other threads:[~2024-11-25  4:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25  4:22 Shrikanth Hegde [this message]
2024-11-25  4:22 ` [PATCH 1/3] powerpc: copy preempt.h into arch/include/asm Shrikanth Hegde
2024-11-26 10:49   ` Christophe Leroy
2024-11-27  6:37   ` Christophe Leroy
2024-12-02 14:05     ` Shrikanth Hegde
2024-12-02 18:17       ` Christophe Leroy
2024-12-03 14:00         ` Shrikanth Hegde
2024-12-03 19:47           ` Christophe Leroy
2024-11-25  4:22 ` [PATCH 2/3] powerpc: support dynamic preemption Shrikanth Hegde
2024-11-26 10:48   ` Christophe Leroy
2024-11-26 11:15     ` Shrikanth Hegde
2024-11-27  6:28       ` Christophe Leroy
2024-11-27  6:44   ` Christophe Leroy
2024-12-01 19:45     ` Shrikanth Hegde
2024-12-03 19:53       ` Christophe Leroy
2024-11-25  4:22 ` [PATCH 3/3] powerpc: print right preemption model in die Shrikanth Hegde
2024-12-04  6:44   ` Christophe Leroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241125042212.1522315-1-sshegde@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=ankur.a.arora@oracle.com \
    --cc=bigeasy@linutronix.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mark.rutland@arm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --cc=vschneid@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).