linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ankur Arora <ankur.a.arora@oracle.com>
Cc: Shrikanth Hegde <sshegde@linux.ibm.com>,
	mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
	npiggin@gmail.com, christophe.leroy@csgroup.eu,
	maddy@linux.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] powerpc: Large user copy aware of full:rt:lazy preemption
Date: Wed, 20 Nov 2024 09:03:12 +0100	[thread overview]
Message-ID: <20241120080312.uHw4eJcQ@linutronix.de> (raw)
In-Reply-To: <874j43hqy8.fsf@oracle.com>

On 2024-11-19 13:08:31 [-0800], Ankur Arora wrote:
> 
> Shrikanth Hegde <sshegde@linux.ibm.com> writes:
> 
> > Large user copy_to/from (more than 16 bytes) uses vmx instructions to
> > speed things up. Once the copy is done, it makes sense to try schedule
> > as soon as possible for preemptible kernels. So do this for
> > preempt=full/lazy and rt kernel.
> 
> Note that this check will also fire for PREEMPT_DYNAMIC && preempt=none.
> So when power supports PREEMPT_DYNAMIC this will need to change
> to preempt_model_*() based checks.
> 
> > Not checking for lazy bit here, since it could lead to unnecessary
> > context switches.
> 
> Maybe:
> Not checking for lazy bit here, since we only want to schedule when
> a context switch is imminently required.

Isn't his behaviour here exactly what preempt_enable() would do?
If the LAZY bit is set, it is delayed until return to userland or an
explicit schedule() because it is done. If this LAZY bit turned into an
actual scheduling request then it is acted upon.

Sebastian


  reply	other threads:[~2024-11-20  8:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 19:23 [PATCH v2 0/2] powerpc: Enable lazy preemption Shrikanth Hegde
2024-11-16 19:23 ` [PATCH v2 1/2] powerpc: Add preempt lazy support Shrikanth Hegde
2024-11-26 10:53   ` Christophe Leroy
2024-12-01 19:28     ` Shrikanth Hegde
2024-12-09  7:43       ` Luming Yu
2024-11-16 19:23 ` [PATCH v2 2/2] powerpc: Large user copy aware of full:rt:lazy preemption Shrikanth Hegde
2024-11-19 21:08   ` Ankur Arora
2024-11-20  8:03     ` Sebastian Andrzej Siewior [this message]
2024-11-20 15:33       ` Shrikanth Hegde
2024-11-20  8:00   ` Sebastian Andrzej Siewior
2024-11-20 18:10     ` Shrikanth Hegde
2024-12-10 11:22 ` [PATCH v2 0/2] powerpc: Enable lazy preemption Shrikanth Hegde
2025-01-01  9:08 ` Madhavan Srinivasan

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=20241120080312.uHw4eJcQ@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=ankur.a.arora@oracle.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=sshegde@linux.ibm.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).