lkml.org 
[lkml]   [2007]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)
On Wed, 15 Aug 2007, Peter Zijlstra wrote:

> The thing I strongly objected to was the 20%.

Well then set it to 10%. We have min_free_kbytes now and so we are used
to these limits.

> Also his approach misses the threshold - the extra condition needed to
> break out of the various network deadlocks. There is no point that says
> - ok, and now we're in trouble, drop anything non-critical. Without that
> you'll always run into a wall.

Networking?

> That is his second patch-set, and I do worry about the irq latency that
> that will introduce. It very much has the potential to ruin everything
> that cares about interactiveness or latency.

Where is the patchset introducing additional latencies? Most of the time
it only saves and restores flags. We already enable and disable interrupts
in the reclaim path but we assume that interupts are always enabled when
we enter reclaim.

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

\
 
 \ /
  Last update: 2007-08-15 22:35    [W:0.122 / U:1.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site