All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20090705151628.GA11307@localhost>

diff --git a/a/1.txt b/N1/1.txt
index e0c83c2..a5500e7 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -2,12 +2,12 @@ On Sun, Jul 05, 2009 at 11:04:17PM +0800, Minchan Kim wrote:
 > On Sun, Jul 5, 2009 at 10:19 PM, KOSAKI
 > Motohiro<kosaki.motohiro@jp.fujitsu.com> wrote:
 > >>> > > + printk("%ld total anon pages\n", global_page_state(NR_ANON_PAGES));
-> >>> > >   printk("%ld total pagecache pages\n", global_page_state(NR_FILE_PAGES));
+> >>> > > A  printk("%ld total pagecache pages\n", global_page_state(NR_FILE_PAGES));
 > >>> >
 > >>> > Can we put related items together, ie. this looks more friendly:
 > >>> >
-> >>> >         Anon:XXX active_anon:XXX inactive_anon:XXX
-> >>> >         File:XXX active_file:XXX inactive_file:XXX
+> >>> > A  A  A  A  Anon:XXX active_anon:XXX inactive_anon:XXX
+> >>> > A  A  A  A  File:XXX active_file:XXX inactive_file:XXX
 > >>>
 > >>> hmmm. Actually NR_ACTIVE_ANON + NR_INACTIVE_ANON != NR_ANON_PAGES.
 > >>> tmpfs pages are accounted as FILE, but it is stay in anon lru.
@@ -28,7 +28,7 @@ On Sun, Jul 05, 2009 at 11:04:17PM +0800, Minchan Kim wrote:
 > >> pages, because the excessive use of tmpfs pages could be a common
 > >> reason of OOM.
 > >
-> > Yeah,  explicite tmpfs/shmem accounting is also useful for /proc/meminfo.
+> > Yeah, A explicite tmpfs/shmem accounting is also useful for /proc/meminfo.
 > 
 > Do we have to account it explicitly?
 
@@ -48,3 +48,9 @@ our little brain ;)
 
 Thanks,
 Fengguang
+
+--
+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>
diff --git a/a/content_digest b/N1/content_digest
index fc4081d..63b6a1f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -21,12 +21,12 @@
  "> On Sun, Jul 5, 2009 at 10:19 PM, KOSAKI\n"
  "> Motohiro<kosaki.motohiro@jp.fujitsu.com> wrote:\n"
  "> >>> > > + printk(\"%ld total anon pages\\n\", global_page_state(NR_ANON_PAGES));\n"
- "> >>> > > \302\240 printk(\"%ld total pagecache pages\\n\", global_page_state(NR_FILE_PAGES));\n"
+ "> >>> > > A  printk(\"%ld total pagecache pages\\n\", global_page_state(NR_FILE_PAGES));\n"
  "> >>> >\n"
  "> >>> > Can we put related items together, ie. this looks more friendly:\n"
  "> >>> >\n"
- "> >>> > \302\240 \302\240 \302\240 \302\240 Anon:XXX active_anon:XXX inactive_anon:XXX\n"
- "> >>> > \302\240 \302\240 \302\240 \302\240 File:XXX active_file:XXX inactive_file:XXX\n"
+ "> >>> > A  A  A  A  Anon:XXX active_anon:XXX inactive_anon:XXX\n"
+ "> >>> > A  A  A  A  File:XXX active_file:XXX inactive_file:XXX\n"
  "> >>>\n"
  "> >>> hmmm. Actually NR_ACTIVE_ANON + NR_INACTIVE_ANON != NR_ANON_PAGES.\n"
  "> >>> tmpfs pages are accounted as FILE, but it is stay in anon lru.\n"
@@ -47,7 +47,7 @@
  "> >> pages, because the excessive use of tmpfs pages could be a common\n"
  "> >> reason of OOM.\n"
  "> >\n"
- "> > Yeah, \302\240explicite tmpfs/shmem accounting is also useful for /proc/meminfo.\n"
+ "> > Yeah, A explicite tmpfs/shmem accounting is also useful for /proc/meminfo.\n"
  "> \n"
  "> Do we have to account it explicitly?\n"
  "\n"
@@ -66,6 +66,12 @@
  "our little brain ;)\n"
  "\n"
  "Thanks,\n"
- Fengguang
+ "Fengguang\n"
+ "\n"
+ "--\n"
+ "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n"
+ "the body to majordomo@kvack.org.  For more info on Linux MM,\n"
+ "see: http://www.linux-mm.org/ .\n"
+ "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>"
 
-fb3a3d5477c218ca59dfeb7eabed4fde7807158fe7300cca953ad473a2a11580
+79a5ba9e28e26edddc2559b430abf50e4476085cebcb66d71a9ebe01cb6d6e3c

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.