From: Nick Piggin <npiggin@suse.de>
To: Dave Airlie <airlied@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
magnade@gmail.com, davej@codemonkey.org.uk
Subject: Re: [patch] agp: don't lock pages
Date: Thu, 26 Jul 2007 04:07:04 +0200 [thread overview]
Message-ID: <20070726020704.GC20727@wotan.suse.de> (raw)
In-Reply-To: <21d7e9970707251844p5c0243d6q7366ab8fa3738f62@mail.gmail.com>
On Thu, Jul 26, 2007 at 11:44:22AM +1000, Dave Airlie wrote:
> >
> >Yeah I had a bit of a look around, and it seems OK (but would
> >appreciate an ack from someone who knows the code).
> >
> >These pages will never get seen by page reclaim, so we're OK
> >there. There is a get_page before the SetPageLocked and a put_page
> >right before the unlock_page, so refcounting should not be broken
> >if it wasn't already: note that the lock_page doesn't pin a
> >reference on a page in general -- we can use it as such for pagecache
> >(although it isn't very clean), because the lock pins the page in
> >pagecache and the pagecache holds a ref.
> >
> >Anyway, if Dave or David can take a look, that would be appreciated.
> >We'll need this for 2.6.23.
>
> I talked with Ben earlier and I can't see anything inherently wrong
> with removing the lock_page, I assume it was put there to stop things
> getting swapped but if the get/put does that then I'd be happy to
> remove it.
Well it is prevented from being swapped out because it never gets
put on swapout lists, but the get/put certainly doesn't hurt :)
> I'm just a bit confused how this didn't get picked up in -mm at all.
Beats me. It was in there for nearly 5 months. Mustn't have been
tested or reported.
prev parent reply other threads:[~2007-07-26 2:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 11:19 Nick Piggin
2007-07-25 18:44 ` Bret Towe
2007-07-25 21:26 ` Benjamin Herrenschmidt
2007-07-26 0:41 ` Nick Piggin
2007-07-26 0:42 ` Nick Piggin
2007-07-26 1:44 ` Dave Airlie
2007-07-26 2:07 ` Nick Piggin [this message]
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=20070726020704.GC20727@wotan.suse.de \
--to=npiggin@suse.de \
--cc=airlied@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.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
all inboxes | Powered by JetHome®