When memory pressure is high, virtio ballooning will probably cause oom
killing.
Even if alloc_page with GFP_NORETRY itself does not directly trigger oom it
will make memory becoming low then memory alloc of other processes will
trigger
oom killing. It is not desired behaviour.
Here
On Tue, Apr 26, 2011 at 2:38 PM, KOSAKI Motohiro
kosaki.motoh...@jp.fujitsu.com wrote:
When memory pressure is high, virtio ballooning will probably cause oom
killing.
Even if alloc_page with GFP_NORETRY itself does not directly trigger oom it
will make memory becoming low then memory
On Wed, Apr 27, 2011 at 9:37 AM, Dave Young hidave.darks...@gmail.com wrote:
On Wed, Apr 27, 2011 at 7:33 AM, Minchan Kim minchan@gmail.com wrote:
On Tue, Apr 26, 2011 at 6:39 PM, Dave Young hidave.darks...@gmail.com
wrote:
On Tue, Apr 26, 2011 at 5:28 PM, Minchan Kim
Hi Dave,
Thanks long explanation.
Secondly, You misparsed avoid direct reclaim paragraph. We don't talk
about avoid direct reclaim even if system memory is no enough, We talk
about avoid direct reclaim by preparing before.
I don't think I misparsed it. I am addressing the avoid direct
On Fri, Apr 01, 2011 at 10:17:56PM +0900, KOSAKI Motohiro wrote:
But, I agree that now we have to concern slightly large VM change
parhaps
(or parhaps not). Ok, it's good opportunity to fill out some thing.
Historically, Linux MM has free memory are waste memory policy
Hm. OK, I may misread.
Can you please explain the reason why de-duplication feature need to
selectable and
disabled by defaut. explicity enable mean this feature want to spot
corner case issue??
Yes, because given a selection of choices (including what you
mentioned
On Fri, 1 Apr 2011, KOSAKI Motohiro wrote:
On Thu, 31 Mar 2011, KOSAKI Motohiro wrote:
1) zone reclaim doesn't work if the system has multiple node and the
workload is file cache oriented (eg file server, web server, mail
server, et al).
because zone recliam make
Hi
1) zone reclaim doesn't work if the system has multiple node and the
workload is file cache oriented (eg file server, web server, mail
server, et al).
because zone recliam make some much free pages than zone-pages_min and
then new page cache request consume nearest node
Hi Christoph,
Thanks, long explanation.
On Thu, 31 Mar 2011, KOSAKI Motohiro wrote:
1) zone reclaim doesn't work if the system has multiple node and the
workload is file cache oriented (eg file server, web server, mail
server, et al).
because zone recliam make some much free
* KOSAKI Motohiro kosaki.motoh...@jp.fujitsu.com [2011-04-01 16:56:57]:
Hi
1) zone reclaim doesn't work if the system has multiple node and the
workload is file cache oriented (eg file server, web server, mail
server, et al).
because zone recliam make some much free
On Wed, Mar 30, 2011 at 11:00:26AM +0530, Balbir Singh wrote:
The following series implements page cache control,
this is a split out version of patch 1 of version 3 of the
page cache optimization patches posted earlier at
Previous posting http://lwn.net/Articles/425851/ and analysis
The following series implements page cache control,
this is a split out version of patch 1 of version 3 of the
page cache optimization patches posted earlier at
Previous posting http://lwn.net/Articles/425851/ and analysis
at http://lwn.net/Articles/419713/
Detailed Description
On 01/05/2011 10:40 AM, KOSAKI Motohiro wrote:
On 01/05/2011 04:39 AM, KOSAKI Motohiro wrote:
On 01/04/2011 08:14 AM, KOSAKI Motohiro wrote:
Also, If pthread_cond_signal() call sys_yield_to imlicitly,
we can
avoid almost Nehalem (and other P2P cache arch
On 01/04/2011 08:14 AM, KOSAKI Motohiro wrote:
Also, If pthread_cond_signal() call sys_yield_to imlicitly, we can
avoid almost Nehalem (and other P2P cache arch) lock unfairness
problem. (probaby creating pthread_condattr_setautoyield_np or similar
knob is good one)
Often, the thread
NAK NAK NAK, yield_to is utter crap, and the only reason kvm 'needs' it
is because its wants to be utter crap (run unmodified guests).
There is plenty of sane serialization primitives for userspace, fix your
locking mess instead of pushing crap.
The only reason I'm maybe half-way
From: Mike Galbraith efa...@gmx.de
Add a yield_to function to the scheduler code, allowing us to
give enough of our timeslice to another thread to allow it to
run and release whatever resource we need it to release.
We may want to use this to provide a sys_yield_to system call
one day.
On Tue, 30 Nov 2010, Andrew Morton wrote:
+#define UNMAPPED_PAGE_RATIO 16
Well. Giving 16 a name didn't really clarify anything. Attentive
readers will want to know what this does, why 16 was chosen and what
the effects of changing it will be.
The meaning is analoguous to the
17 matches
Mail list logo
