Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 191392
b: refs/heads/master
c: c6ee36c
h: refs/heads/master
v: v3
  • Loading branch information
Mike Galbraith authored and Ingo Molnar committed Mar 11, 2010
1 parent be89796 commit 7054130
Show file tree
Hide file tree
Showing 3 changed files with 1 addition and 12 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: f2e74eeac03ffb779d64b66a643c5e598145a28b
refs/heads/master: c6ee36c423c3ed1fb86bb3eabba9fc256a300d16
3 changes: 0 additions & 3 deletions trunk/kernel/sched.c
Original file line number Diff line number Diff line change
Expand Up @@ -2369,9 +2369,6 @@ static int try_to_wake_up(struct task_struct *p, unsigned int state,
unsigned long flags;
struct rq *rq;

if (!sched_feat(SYNC_WAKEUPS))
wake_flags &= ~WF_SYNC;

this_cpu = get_cpu();

smp_wmb();
Expand Down
8 changes: 0 additions & 8 deletions trunk/kernel/sched_features.h
Original file line number Diff line number Diff line change
Expand Up @@ -22,14 +22,6 @@ SCHED_FEAT(WAKEUP_PREEMPT, 1)
*/
SCHED_FEAT(ASYM_GRAN, 1)

/*
* Use the SYNC wakeup hint, pipes and the likes use this to indicate
* the remote end is likely to consume the data we just wrote, and
* therefore has cache benefit from being placed on the same cpu, see
* also AFFINE_WAKEUPS.
*/
SCHED_FEAT(SYNC_WAKEUPS, 1)

/*
* Based on load and program behaviour, see if it makes sense to place
* a newly woken task on the same cpu as the task that woke it --
Expand Down

0 comments on commit 7054130

Please sign in to comment.