linux-kernel - NEPOTISM_BONUS yield_to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20110610171317.GA15253@jim.domain_not_set.invalid>
Date:	Fri, 10 Jun 2011 12:13:17 -0500
From:	Robert Redelmeier <redelm@...global.net>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Robert Redelmeier <redelm@...global.net>
Subject: NEPOTISM_BONUS  yield_to_child() ?

  		[YAFR - Yet Another Feature Request]

Multi-threaded/tasking performance is entirely 
dependent on the OS scheduler.  I searched
	/usr/src/linux/Documentation/scheduler/*
and found no mention of parent or child processes.

Parent- and child-processes are interconnected, and for maximum [SMP] 
performance, these connections should be recognized _optimally._

For example, on some [desktop] systems, an exec() syscall would run
unblocked, an exit() would return the rest of the timeslice to the
parent, yield() would go to child (parent?), etc.  Other servers
might choose the exact opposite.

This connectivity could be implemented by a tuneable scheduler param:

  NEPOTISM_BONUS = int

where positive values would influence the scheduler to run
parents/children/uncles/nieces and negative values would
cause the scheduler to prefer strangers [unrelated procs].

-- Robert in Houston

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/