From: Andrew Morton <akpm@zip.com.au>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-mm@kvack.org
Date: Mon, 02 Sep 2002 12:11:45 -0700 [thread overview]
Message-ID: <3D73B7F1.2EB3131E@zip.com.au> (raw)
In-Reply-To: 20020902204138.A31717@lst.de
Christoph Hellwig wrote:
>
> On Mon, Sep 02, 2002 at 11:50:33AM -0700, Andrew Morton wrote:
> > Christoph Hellwig wrote:
> > >
> > > This patch was done after Linus requested it when I intended to split
> > > madvice out of filemap.c. We extend splitvma() in mmap.c to take
> > > another argument that specifies whether to split above or below the
> > > address given, and thus can use it in those function, cleaning them up
> > > a lot and removing most of their code.
> > >
> >
> > This description seems to have leaked from a different patch.
> >
> > Your patch purely shuffles code about, yes?
>
> No. it makes madvise/mlock/mprotect use slit_vma (that involved from
> splitvma). There is no change in behaviour (verified by ltp testruns),
> but the implementation is very different, and lots of code is gone.
did you send the right patch?
mnm:/usr/src/25> grep split patches/madvise-move.patch
- * We can potentially split a vm area into separate
+ * We can potentially split a vm area into separate
mnm:/usr/src/25> diffstat patches/madvise-move.patch
Makefile | 2
filemap.c | 332 ------------------------------------------------------------
madvise.c | 340 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 342 insertions(+), 332 deletions(-)
--
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/
next prev parent reply other threads:[~2002-09-02 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 17:43 Christoph Hellwig
2002-09-02 18:50 ` Andrew Morton
2002-09-02 18:41 ` Christoph Hellwig
2002-09-02 19:11 ` Andrew Morton [this message]
2002-09-02 19:04 ` Christoph Hellwig
2002-09-02 21:17 ` Andrew Morton
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=3D73B7F1.2EB3131E@zip.com.au \
--to=akpm@zip.com.au \
--cc=hch@lst.de \
--cc=linux-mm@kvack.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 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.