linux-kernel - [PATCH 2/3] mm/readahead: Remove file_ra_state from arguments of count_history

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 10 Jul 2011 01:11:19 +0530
From:	Raghavendra D Prabhu <raghu.prabhu13@...il.com>
To:	fengguang.wu@...el.com
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org,
	Raghavendra D Prabhu <rprabhu@...hang.net>
Subject: [PATCH 2/3] mm/readahead: Remove file_ra_state from arguments of count_history_pages.

count_history_pages doesn't require readahead state to calculate the offset from history.

Signed-off-by: Raghavendra D Prabhu <rprabhu@...hang.net>
---
 mm/readahead.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/mm/readahead.c b/mm/readahead.c
index 867f9dd..925d3b3 100644
--- a/mm/readahead.c
+++ b/mm/readahead.c
@@ -343,7 +343,6 @@ static unsigned long get_next_ra_size(struct file_ra_state *ra,
  * 	- thrashing threshold in memory tight systems
  */
 static pgoff_t count_history_pages(struct address_space *mapping,
-				   struct file_ra_state *ra,
 				   pgoff_t offset, unsigned long max)
 {
 	pgoff_t head;
@@ -366,7 +365,7 @@ static int try_context_readahead(struct address_space *mapping,
 {
 	pgoff_t size;
 
-	size = count_history_pages(mapping, ra, offset, max);
+	size = count_history_pages(mapping, offset, max);
 
 	/*
 	 * no history pages:
-- 
1.7.6

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