From: Ethan Solomita <solo@google.com>
To: linux-mm@kvack.org
Subject: [RFC 6/7] cpuset write fixes
Date: Mon, 23 Apr 2007 16:33:18 -0700 [thread overview]
Message-ID: <462D423E.4060904@google.com> (raw)
In-Reply-To: <462D3F4C.2040007@google.com>
Remove unneeded local variable.
Originally by Christoph Lameter <clameter@sgi.com>
Signed-off-by: Ethan Solomita <solo@google.com>
---
diff -uprN -X linux-2.6.21-rc4-mm1/Documentation/dontdiff 5/mm/page-writeback.c 6/mm/page-writeback.c
--- 5/mm/page-writeback.c 2007-04-23 15:13:15.000000000 -0700
+++ 6/mm/page-writeback.c 2007-04-23 15:14:25.000000000 -0700
@@ -177,7 +177,6 @@ get_dirty_limits(struct dirty_limits *dl
int unmapped_ratio;
long background;
long dirty;
- unsigned long available_memory = determine_dirtyable_memory();
unsigned long dirtyable_memory;
unsigned long nr_mapped;
struct task_struct *tsk;
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-04-23 23:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 23:20 [RFC 1/7] cpuset write dirty map Ethan Solomita
2007-04-23 23:30 ` [RFC 2/7] cpuset write pdflush nodemask Ethan Solomita
2007-04-23 23:31 ` [RFC 3/7] cpuset write throttle Ethan Solomita
2007-04-23 23:31 ` [RFC 4/7] cpuset write vmscan Ethan Solomita
2007-04-23 23:35 ` [Corrected] " Ethan Solomita
2007-04-23 23:32 ` [RFC 5/7] cpuset write vm writeout Ethan Solomita
2007-04-23 23:33 ` Ethan Solomita [this message]
2007-04-23 23:33 ` [RFC 7/7] cpuset dirty limits Ethan Solomita
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 6:03 [RFC 1/7] cpuset write dirty map Ethan Solomita
2007-06-01 6:16 ` [RFC 6/7] cpuset write fixes Ethan Solomita
2007-06-01 6:16 ` Ethan Solomita
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462D423E.4060904@google.com \
--to=solo@google.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.