From: Eric Dumazet <eric.dumazet@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: Shaohua Li <shaohua.li@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>, Lin Ming <mlin@ss.pku.edu.cn>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Pawel Sikora <pluto@agmk.net>
Subject: Re: [BUG] infinite loop in find_get_pages()
Date: Thu, 15 Sep 2011 00:08:09 +0200 [thread overview]
Message-ID: <1316038089.2835.4.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.LSU.2.00.1109141427190.29355@sister.anvils>
Le mercredi 14 septembre 2011 à 14:53 -0700, Hugh Dickins a écrit :
> On Wed, 14 Sep 2011, Eric Dumazet wrote:
> > Le mercredi 14 septembre 2011 à 13:38 -0700, Hugh Dickins a écrit :
> > >
> > > I'd like to think about that a little more before finalizing the
> > > patch below - does it work, and does it look acceptable so far?
> > > Of course, the mods to truncate.c and vmscan.c are not essential
> > > parts of this fix, just things to tidy up while on the subject.
> > > Right now I must attend to some other stuff, will return tomorrow.
> >
> > Hello Hugh
> >
> > I am going to test this ASAP,
>
> Thanks, Eric, though it may not be worth spending your time on it.
> It occurred to me over lunch that it may take painfully longer than
> expected to invalidate_mapping_pages() on a single-swapped-out-page
> 1TB sparse tmpfs file - all those "start += 1" restarts until it
> reaches the end.
>
> I might decide to leave invalidate_mapping_pages() giving up early
> (unsatisfying, but no worse than before), and convert scan_mapping_
> unevictable_pages() (which is used on nothing but shmem) to pass
> index vector to radix_tree_gang_whatever().
>
> Dunno, I'll think about it more later.
>
I tested your patch as is on my machine, and everything seems fine.
I let the stress continue while I am going to sleep :)
See you
next prev parent reply other threads:[~2011-09-14 22:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 19:23 Eric Dumazet
2011-09-13 23:53 ` Andrew Morton
2011-09-14 0:21 ` Eric Dumazet
2011-09-14 0:34 ` Lin Ming
2011-09-15 10:47 ` Pawel Sikora
2011-09-15 11:11 ` Justin Piszcz
2011-09-15 12:04 ` Eric Dumazet
2011-09-15 15:00 ` Paweł Sikora
2011-09-15 15:15 ` Eric Dumazet
[not found] ` <CA+55aFyG3-3_gqGjqUmsTAHWfmNLMdQVf4XqUZrDAGMBxgur=Q@mail.gmail.com>
2011-09-14 6:48 ` Linus Torvalds
2011-09-14 6:53 ` Eric Dumazet
2011-09-14 7:32 ` Shaohua Li
2011-09-14 8:20 ` Shaohua Li
2011-09-14 8:43 ` Eric Dumazet
2011-09-14 8:55 ` Shaohua Li
2011-09-14 20:38 ` Hugh Dickins
2011-09-14 20:55 ` Eric Dumazet
2011-09-14 21:53 ` Hugh Dickins
2011-09-14 22:08 ` Eric Dumazet [this message]
2011-09-14 22:37 ` Linus Torvalds
2011-09-15 0:45 ` Shaohua Li
2011-09-15 2:00 ` Hugh Dickins
2011-09-15 4:02 ` Eric Dumazet
[not found] ` <CA+55aFx41_Z4TjjJwPuE21Q8oD3aGWtQwh45DUiCjPVD-wCJXw@mail.gmail.com>
2011-09-14 6:48 ` Linus Torvalds
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=1316038089.2835.4.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlin@ss.pku.edu.cn \
--cc=pluto@agmk.net \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®