On Mon, May 13, 2019 at 01:24:57PM -0700, Doug Anderson wrote: > On Sun, May 12, 2019 at 10:05 AM Mark Brown <broonie@xxxxxxxxxx> wrote: > > If performance is important you probably also want to avoid the context > > thrashing - executing in the calling context is generally a substantial > > performance boost. I can see this causing problems further down the > > line when someone else turns up with a different requirement, perhaps in > > an application where the caller does actually have a raised priority > > themselves and just wanted to make sure that the thread wasn't lower > > than they are. I guess it'd be nice if we could check what priority the > > calling thread has and make a decision based on that but there don't > > seem to be any facilities for doing that which I can see right now. > In my case performance is 2nd place to a transfer not getting > interrupted once started (so we don't break the 8ms rule of the EC). That's great but other users do care very much about performance and are also interested in both priority control and avoiding context thrashing. > My solution in v2 of my series is to take out the forcing in the case > that the controller wanted "rt" priority and then to add "force" to > the parameter name. If someone wants rt priority for the thread but > doesn't want to force all transfers to the thread we can later add a > different parameter for that? I think that's going to be the common case for this. Forcing context thrashing is really not something anyone else is asking for.
Attachment:
signature.asc
Description: PGP signature
