Re: [PATCH 5/5] cpuset: memory reclaim rate meter

> I guess I'll give up and merge this thing.

Actually - definitely wait for the next version.

Kill the version you have of this patch.

I just realized that "memory_reclaim_rate" was a bogus
name for this feature.  The users, batch managers, don't
give a dang that its hooked into some direct reclaim
point in the kernel.

They just want a decent measure of memory pressure in
a cpuset.

So I am going to rename the flag, to "memory_pressure".

Kill the current 'memory reclaim rate' patch.  I will
resend in perhaps an hour, under this new name.

-- 
                  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/

---

• References:
  • [PATCH 1/5] cpuset: better bitmap remap defaults
    • From: Paul Jackson <[email protected]>
  • [PATCH 5/5] cpuset: memory reclaim rate meter
    • From: Paul Jackson <[email protected]>
  • Re: [PATCH 5/5] cpuset: memory reclaim rate meter
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [PATCH 5/5] cpuset: memory reclaim rate meter
• Next by Date: Re: [PATCH] [IPV4] Fix secondary IP addresses after promotion
• Previous by thread: Re: [PATCH 5/5] cpuset: memory reclaim rate meter
• Next by thread: Re: [PATCH 5/5] cpuset: memory reclaim rate meter
• 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]