From: Ray Bryant <raybry@sgi.com>
To: linux-mm <linux-mm@kvack.org>
Cc: Nick Piggin <piggin@cyberone.com.au>
Subject: lru_add_drain query
Date: Thu, 03 Feb 2005 11:22:23 -0600 [thread overview]
Message-ID: <42025DCF.2080004@sgi.com> (raw)
The deferred lru_add operations (e. g. lru_cache_add_active()) defer the
actual addition of a page to the lru list until a batch of such additions
are available. lru_cache_add_active() uses a per cpu variable
(lru_add_active_pvecs) to hold the deferred pages.
So, to get the deferred adds to complete (so that the lru list is in a
consistent state and we can scan lru list to do some processing) one calls
lru_add_drain(). But AFAI can tell, this just drains the local cpu's
deferred add queue. Right?
So, here's my question: Why is it that I don't need to call lru_add_drain()
on each CPU in the system before I go scan/manipulate the lru list? (i. e.
what about deferred adds in other CPU's lru_add_active_pvecs?)
What peice of magic am I missing here?
Thanks,
--
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
--
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:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2005-02-03 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 17:22 Ray Bryant [this message]
2005-02-03 23:50 ` lru_add_drain query Nick Piggin
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=42025DCF.2080004@sgi.com \
--to=raybry@sgi.com \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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 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.