From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: [patch 2/13] remove pages from the LRU in __free_pages_ok()
Date: Sun, 28 Jul 2002 23:10:17 -0700 (PDT) [thread overview]
Message-ID: <20020728.231017.40779367.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207282256460.872-100000@home.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Sun, 28 Jul 2002 23:16:24 -0700 (PDT)
[ This is Linus speaking in all the quoted material below... ]
> But the thing is, nobody should normally have a reference to such a
> page anyway. The only way they happen is by something mapping a
> page from user space, and saving it away, while the user space goes
> away and drops its references to the page.
...
But hopefully nobody should have the problematic last reference to a LRU
page _except_ the user space itself. That should be safe for page cache
pages thanks to the truncate change.
[ Now DaveM is talking :-) ]
So let's say that we have a page going out a socket. The socket's FD
has multiple references so when the user exit()'s the anonymous page
is still "in-flight" but the socket isn't closed and thus we won't
wait for the write to complete.
So when the user's reference is dropped, does that operation kill it
from the LRU or will the socket's remaining reference to that page
defer the LRU removal?
next prev parent reply other threads:[~2002-07-29 6:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 7:32 [patch 2/13] remove pages from the LRU in __free_pages_ok() Andrew Morton
2002-07-28 23:54 ` Linus Torvalds
2002-07-29 0:32 ` Andrew Morton
2002-07-29 0:37 ` Linus Torvalds
2002-07-29 0:59 ` Andrew Morton
2002-07-29 0:59 ` Rik van Riel
2002-07-29 2:50 ` David S. Miller
2002-07-29 3:51 ` Linus Torvalds
2002-07-29 3:43 ` David S. Miller
2002-07-29 4:21 ` Linus Torvalds
2002-07-29 5:43 ` David S. Miller
2002-07-29 6:16 ` Linus Torvalds
2002-07-29 6:10 ` David S. Miller [this message]
2002-07-29 6:27 ` Linus Torvalds
2002-07-29 6:59 ` Andrew Morton
2002-07-30 11:30 ` Ed Tomlinson
[not found] ` <200208011942.49342.tomlins@cam.org>
[not found] ` <3D49C951.AB7C527E@zip.com.au>
2002-08-03 19:27 ` [PATCH] slablru for linux-2.5 bk tree Ed Tomlinson
2002-08-03 20:43 ` Rik van Riel
2002-08-04 3:17 ` Andrew Morton
2002-07-29 8:35 ` [patch 2/13] remove pages from the LRU in __free_pages_ok() Rik van Riel
2002-07-29 4:25 ` Andrew Morton
2002-07-29 4:28 ` Linus Torvalds
2002-07-29 4:52 ` Andrew Morton
2002-07-29 4:50 ` Linus Torvalds
2002-07-29 5:15 ` Andrew Morton
2002-07-29 4:17 ` Andrew Morton
2002-07-29 4:23 ` Linus Torvalds
2002-07-29 5:43 ` David S. Miller
2002-07-29 6:24 ` Paul Mackerras
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=20020728.231017.40779367.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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