Re: cpusets: only wakeup kswapd for zones in the current cpuset

> None if that is the case.

Take a look at wakeup_kswapd() for yourself ;).
No need to speculate.

Do you recall why you posted this patch?  The
wording made it sound like you had hit some
problem with waking up kswapd for all the nodes.

If you really saw that, then it would seem that
we still have a problem, that is now lacking a fix.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: cpusets: only wakeup kswapd for zones in the current cpuset
    • From: Christoph Lameter <[email protected]>

• References:
  • Re: cpusets: only wakeup kswapd for zones in the current cpuset
    • From: Paul Jackson <[email protected]>
  • Re: cpusets: only wakeup kswapd for zones in the current cpuset
    • From: Christoph Lameter <[email protected]>

• Prev by Date: Re: Linux Kernel Source Compression
• Next by Date: Re: NMI problems with Dell SMP Xeons
• Previous by thread: Re: cpusets: only wakeup kswapd for zones in the current cpuset
• Next by thread: Re: cpusets: only wakeup kswapd for zones in the current cpuset
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]