* issue with direct reclaims and kswapd reclaims on 2.6.35.7
@ 2011-08-15 5:08 Jeffrey Vanhoof
2011-08-18 6:47 ` Jeffrey Vanhoof
0 siblings, 1 reply; 2+ messages in thread
From: Jeffrey Vanhoof @ 2011-08-15 5:08 UTC (permalink / raw)
To: linux-mm
On a 2.6.35.7 based kernel, on a portable device with 512MB RAM, I am
seeing the following issues while consuming 20Mbps video content:
1) direct reclaims occurring quite frequently, resulting in delayed
file read requests
2) direct reclaims falling into congestion_wait() even though no
congestion at the time, this results in video jitter.
3) kswapd not reclaiming pages quickly enough due to falling into
congestion_wait() very often.
4) power consumption is degraded as a result of time being spent in
io_schedule_timeout() called within congestion_wait(). (the power
c-state will stay in C0)
Are there specific patches which can be easily back-ported to K35
which may address most of these issues?
For file read performance, I believe it is better for kswapd to
reclaim memory instead of hitting a direct reclaim, and for power it
would be best that while reclaiming memory in kswapd that
io_schedule()/io_schedule_timeout() is never called unless absolutely
required.
Are any of the workarounds listed below appropriate to use?
1) change the congestion_wait() timeout value in balance_pgdat() from
HZ/10 to HZ/50. This allows for faster reclaims in kswapd and limits
the time spend in congestion_wait().
2) change SWAP_CLUSTER_MAX from 32 to 128 or higher (swap is enabled,
but there is no swap).
3) change DEF_PRIORITY from 12 to 9. This results in a larger scan and
pages are reclaimed quicker. Also, this causes congestion_wait() to be
called less frequently due to the likelyhood of pages being found with
increase priority.
Any help would be appreciated.
Thanks,
Jeff V.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: issue with direct reclaims and kswapd reclaims on 2.6.35.7
2011-08-15 5:08 issue with direct reclaims and kswapd reclaims on 2.6.35.7 Jeffrey Vanhoof
@ 2011-08-18 6:47 ` Jeffrey Vanhoof
0 siblings, 0 replies; 2+ messages in thread
From: Jeffrey Vanhoof @ 2011-08-18 6:47 UTC (permalink / raw)
To: linux-mm; +Cc: tghk48
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
w.r.t:
> 1) direct reclaims occurring quite frequently, resulting in delayed
> file read requests
> 2) direct reclaims falling into congestion_wait() even though no
> congestion at the time, this results in video jitter.
Backporting the following changes seemed to greatly improve these issues:
-vmscan: synchronous lumpy reclaim should not call congestion_wait()
-writeback: do not sleep on the congestion queue if there are no
congested BDIs or if significant congestion is not being encountered
in the current zone
-vmscan: avoid setting zone congested if no page dirty
w.r.t.:
> 3) kswapd not reclaiming pages quickly enough due to falling into
> congestion_wait() very often. (or stays in congestion_wait() for too long)
The attached patch takes an idea from Mel Gorman's patch for
"writeback: do not sleep on the congestion queue if there are no
congested BDIs or if significant congestion is not being encountered
in the current zone" and applies it around the congestion_wait() in
balance_pgdat(). The idea is that if there is no congestion then avoid
potentially wait for too long. Comments or alternate solutions would
be appreciated.
Thanks,
Jeff Vanhoof
[-- Attachment #2: k35_kswapd_query_iff_congested_workaround.txt --]
[-- Type: text/plain, Size: 3196 bytes --]
commit af8ebaca0d367e14b49a151731e8a3e9bc6685f1
Author: Jeff Vanhoof <jdv1029@gmail.com>
Date: Tue Aug 16 00:14:31 2011 -0500
linux-mm: Improve kswapd reclaimation of memory
This is a workaround to improve the number of pages reclaimed
in kswapd so that direct reclaims and iowaits are minimized.
Change-Id: I491e9c80809b5ec3e1e7807742807a2317fc2394
diff --git a/include/linux/backing-dev.h b/include/linux/backing-dev.h
index fa79632..e5b6d3d 100644
--- a/include/linux/backing-dev.h
+++ b/include/linux/backing-dev.h
@@ -286,6 +286,7 @@ void clear_bdi_congested(struct backing_dev_info *bdi, int sync);
void set_bdi_congested(struct backing_dev_info *bdi, int sync);
long congestion_wait(int sync, long timeout);
long wait_iff_congested(struct zone *zone, int sync, long timeout);
+int query_iff_congested(struct zone *zone, int sync);
static inline bool bdi_cap_writeback_dirty(struct backing_dev_info *bdi)
{
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index 4254946..fcf7976 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -850,3 +850,32 @@ out:
return ret;
}
EXPORT_SYMBOL(wait_iff_congested);
+
+/**
+ * query_iff_congested - Checks if a backing_dev (any backing_dev) is
+ * congested or if the given @zone has has experienced recent congestion.
+ * @zone: A zone to check if it is heavily congested
+ * @sync: SYNC or ASYNC IO
+ *
+ * The return value is 1 if either backing_dev (any) or @zone is congested,
+ * otherwise 0 is returned.
+ *
+ */
+int query_iff_congested(struct zone *zone, int sync)
+{
+ long ret = 1;
+ DEFINE_WAIT(wait);
+ wait_queue_head_t *wqh = &congestion_wqh[sync];
+
+ /*
+ * If there is no congestion, or heavy congestion is not being
+ * encountered in the current zone, set ret to 0
+ */
+ if (atomic_read(&nr_bdi_congested[sync]) == 0 ||
+ !zone_is_reclaim_congested(zone)) {
+ ret = 0;
+ }
+
+ return ret;
+}
+EXPORT_SYMBOL(query_iff_congested);
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 1bd01ee..e8686f0 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -2169,6 +2169,7 @@ loop_again:
int end_zone = 0; /* Inclusive. 0 = ZONE_DMA */
unsigned long lru_pages = 0;
int has_under_min_watermark_zone = 0;
+ int any_zone_congested = 0;
/* The swap token gets in the way of swapout... */
if (!priority)
@@ -2294,6 +2295,13 @@ loop_again:
}
if (all_zones_ok)
break; /* kswapd: all done */
+
+ /* Check to see if any zones are congested */
+ for (i = pgdat->nr_zones - 1; i >= 0; i--) {
+ struct zone *zone = pgdat->node_zones + i;
+ any_zone_congested |=
+ query_iff_congested(zone, BLK_RW_ASYNC);
+ }
+
/*
* OK, kswapd is getting into trouble. Take a nap, then take
* another pass across the zones.
@@ -2301,6 +2309,9 @@ loop_again:
if (total_scanned && (priority < DEF_PRIORITY - 2)) {
if (has_under_min_watermark_zone)
count_vm_event(KSWAPD_SKIP_CONGESTION_WAIT);
+ else if (!any_zone_congested &&
+ (priority > DEF_PRIORITY - 8))
+ congestion_wait(BLK_RW_ASYNC, HZ/50);
else
congestion_wait(BLK_RW_ASYNC, HZ/10);
}
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-08-18 6:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-15 5:08 issue with direct reclaims and kswapd reclaims on 2.6.35.7 Jeffrey Vanhoof
2011-08-18 6:47 ` Jeffrey Vanhoof
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).