From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Chen Gang <gang.chen.5i5j@gmail.com>,
Minchan Kim <minchan@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"rth@twiddle.net" <rth@twiddle.net>,
"ink@jurassic.park.msu.ru" <ink@jurassic.park.msu.ru>,
"mattst88@gmail.com" <mattst88@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
"jejb@parisc-linux.org" <jejb@parisc-linux.org>,
"deller@gmx.de" <deller@gmx.de>,
"chris@zankel.net" <chris@zankel.net>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] arch: uapi: asm: mman.h: Support MADV_FREE for madvise()
Date: Mon, 01 Dec 2014 17:55:31 -0800 [thread overview]
Message-ID: <1417485331.2585.26.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAE2sS1hDXqLvF9yY5-3d4pmDPiQy8aQ1fYov3_+BKM8uQ3ZSwA@mail.gmail.com>
On Mon, 2014-12-01 at 17:01 -0500, Carlos O'Donell wrote:
> On Mon, Dec 1, 2014 at 4:35 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Mon, Dec 1, 2014 at 9:52 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
> >> On Mon, Dec 1, 2014 at 11:43 PM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
> >>> At present, kernel supports madvise(MADV_FREE), so can benefit to all
> >>> related architectures (can grep MADV_WILLNEED or MADV_REMOVE in "arch/"
> >>> to know about all related architectures).
> >>
> >> A similar patch has been posted a while ago:
> >>
> >> http://www.spinics.net/lists/linux-mm/msg81538.html
> >
> > Would it be possible to use the same number everywhere?
>
> Yes please. It's ridiculous that we still need patches like this.
>
> I proposed unifying all this two years ago, but didn't follow up.
>
> From glibc's perspective it would be simpler if we started using the
> same number everywhere.
>
> http://www.spinics.net/lists/linux-api/msg02064.html
Please co-ordinate with Andrew then because he's intent on merging this
patch:
http://marc.info/?l=linux-mm-commits&m=141747572930808
James
next prev parent reply other threads:[~2014-12-02 1:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 20:43 [PATCH] arch: uapi: asm: mman.h: Support MADV_FREE for madvise() Chen Gang
2014-12-01 20:52 ` Max Filippov
2014-12-01 21:35 ` Geert Uytterhoeven
2014-12-01 22:01 ` Carlos O'Donell
2014-12-02 1:55 ` James Bottomley [this message]
2014-12-02 2:07 ` Chen Gang
2014-12-02 1:56 ` Chen Gang
-- strict thread matches above, loose matches on Subject: below --
2014-12-01 20:43 Chen Gang
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=1417485331.2585.26.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=carlos@systemhalted.org \
--cc=chris@zankel.net \
--cc=deller@gmx.de \
--cc=gang.chen.5i5j@gmail.com \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jcmvbkbc@gmail.com \
--cc=jejb@parisc-linux.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=mattst88@gmail.com \
--cc=minchan@kernel.org \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for NNTP newsgroup(s).