linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: marc.smith@esmail.mcc.edu,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: VM/VFS bug with large amount of memory and file systems?
Date: Sat, 15 Sep 2007 13:19:01 +0200	[thread overview]
Message-ID: <1189855141.21778.307.camel@twins> (raw)
In-Reply-To: <C9A68AAE-0B37-4BB5-A9E6-66C186566940@cam.ac.uk>

On Sat, 2007-09-15 at 11:50 +0100, Anton Altaparmakov wrote:
> Hi,
> 
> Thanks for looking into this.
> 
> On 15 Sep 2007, at 11:08, Peter Zijlstra wrote:
> > On Sat, 2007-09-15 at 08:27 +0100, Anton Altaparmakov wrote:
> >
> > Please, don't word wrap log-files, they're hard enough to read without
> > it :-(
> >
> > ( I see people do this more and more often, *WHY*? is that because we
> > like 80 char lines, in code and email? )
> 
> I haven't word wrapped it at all.  The lines appear as whole lines in  
> Apple Mail (my email client).  It must be your email client that is  
> wrapping them...
> 
> > Anyway, looks like all of zone_normal is pinned in kernel allocations:
> >
> >> Sep 13 15:31:25 escabot Normal free:3648kB min:3744kB low:4680kB  
> >> high: 5616kB active:0kB inactive:3160kB present:894080kB  
> >> pages_scanned:5336 all_unreclaimable? yes
> >

Oddly, this line is still long in Andrew's reply but wrapped in yours.
Must be some odd mailer interaction.

/me apologises.

I guess I really have to start looking for a hackable GUI email client
that has semi proper IMAP support.

--
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>

  reply	other threads:[~2007-09-15 11:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15  7:27 Anton Altaparmakov
2007-09-15 10:08 ` Peter Zijlstra
2007-09-15 10:50   ` Anton Altaparmakov
2007-09-15 11:19     ` Peter Zijlstra [this message]
2007-09-16  7:22       ` Kyle Moffett
2007-09-16 16:16         ` Peter Zijlstra
2007-09-15 10:52   ` Andrew Morton
2007-09-17 14:04     ` Anton Altaparmakov
2007-09-17 14:09       ` Anton Altaparmakov
2007-09-16 22:28         ` Nick Piggin
2007-09-17 17:04           ` Rik van Riel
2007-09-17 17:12             ` Nick Piggin
2007-09-18 14:41               ` Rik van Riel
2007-09-17 14:32       ` Peter Zijlstra
2007-09-17 17:11         ` Rik van Riel
2007-09-17 20:15           ` Andrew Morton
2007-09-17 20:46             ` Rik van Riel
2007-09-17 21:11               ` Andrew Morton
2007-09-19 22:12                 ` Rik van Riel
2007-09-19 22:45                   ` Andrew Morton
2007-09-19 22:50                     ` Rik van Riel
2007-09-19 23:29                     ` Christoph Lameter
2007-09-19 23:37                       ` Andrew Morton
2007-10-03 10:51 ` Pavel Machek

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=1189855141.21778.307.camel@twins \
    --to=peterz@infradead.org \
    --cc=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marc.smith@esmail.mcc.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox