From: Andrea Arcangeli <andrea@novell.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Hugh Dickins <hugh@veritas.com>,
ak@suse.de, 76306.1226@compuserve.com,
linux-kernel@vger.kernel.org
Subject: Re: Dropped patch: mm/mempolicy.c:sp_lookup()
Date: Thu, 18 Nov 2004 04:08:18 +0100 [thread overview]
Message-ID: <20041118030818.GE28571@dualathlon.random> (raw)
In-Reply-To: <20041117122123.6162fa70.akpm@osdl.org>
On Wed, Nov 17, 2004 at 12:21:23PM -0800, Andrew Morton wrote:
> Sigh. OK, I'll split the patch into three and will feed the `<=' fix and
> the symlink fix into 2.6.10. [..]
thanks.
> [..] The mempolicy optimisation can await 2.6.11.
sure.
About Hugh's version of the shmem.c part, I'm fine with it, but I find
more robust to destroy the mpol in the delete_inode callback than in
delete_inode (for shmfs is the same due the dcache pin), since delete_inode
is normally associated with the unlink operation, but the mpol must go
away before the inode is freed, and the inode is freed in the
destroy_inode (again for shmfs it's the same as delete_inode), plus I
find my version a bit simpler.
As Hugh said as far as one of the two ges merged I'm fine of course ;).
next prev parent reply other threads:[~2004-11-18 3:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 3:54 Dropped patch: mm/mempolicy.c:sp_lookup() Chuck Ebbert
2004-11-17 12:08 ` Andi Kleen
2004-11-17 19:13 ` Andrew Morton
2004-11-17 20:06 ` Hugh Dickins
2004-11-17 20:21 ` Andrew Morton
2004-11-17 20:29 ` Andrew Morton
2004-11-18 5:05 ` Andi Kleen
2004-11-18 3:08 ` Andrea Arcangeli [this message]
2004-11-18 3:08 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 4:15 Chuck Ebbert
2004-11-17 1:00 ` Andi Kleen
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=20041118030818.GE28571@dualathlon.random \
--to=andrea@novell.com \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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