No, it didn't fix it. I'm still getting "eth0: card reports no resources"
from my Intel express card and then system hang when I ran SPEC SFS with
high IOPS request rate, like 4000 IOPS. Is this guess not tight enough? It
seems that the number needs to be calculated based on the processor speed
and the underlying disk subsystem speed, and the total amount of memory...
Ying
The attached patch should alleviate the situation quite a
lot. It guesstimates that 1/3rd of the cache is "freeable"
and old data and takes only that amount into account. The
30% should be about right in heavy write situations because
if we never fill that much cache memory with our writes there
would be no need to do write throttling.
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--- mm/page_alloc.c.orig Wed Aug 2 10:59:45 2000
+++ mm/page_alloc.c Wed Aug 2 11:01:22 2000
@@ -340,7 +340,7 @@
zone_t *zone;
int i;
- sum = nr_lru_pages;
+ sum = nr_lru_pages / 3;
for (i = 0; i < NUMNODES; i++)
for (zone = NODE_DATA(i)->node_zones; zone <=
NODE_DATA(i)->node_zones+ZONE_NORMAL; zone++)
sum += zone->free_pages;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Aug 07 2000 - 21:00:09 EST