linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Hugh Dickins <hugh@veritas.com>, Chris Wright <chrisw@osdl.org>,
	Jeff Dike <jdike@addtoit.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH] OVERCOMMIT_ALWAYS extension
Date: Wed, 19 Oct 2005 12:12:15 -0700	[thread overview]
Message-ID: <43569A8F.4040300@us.ibm.com> (raw)
In-Reply-To: <1129747855.8716.12.camel@localhost.localdomain>

Badari Pulavarty wrote:
>> ...
>>I say "as far as it goes" because I don't think it's actually going to
>>achieve the effect you said you wanted in your original post.
>>
>>As you've probably noticed, switching off VM_ACCOUNT here will mean that
>>the shm object is accounted page by page as it's instantiated, and I
>>expect you're okay with that.  But you want madvise(DONTNEED) to free
>>up those reservations: it'll unmap the pages from userspace, but it
>>won't free the pages from the shm object, so the reservations will
>>still be in force, and accumulate.
> 
> 
> Darren Hart is working on patch to add madvise(DISCARD) to extend
> the functionality of madvise(DONTNEED) to really drop those pages.
> I was going to ask your opinion on that approach :) 
> 
> shmget(SHM_NORESERVE) + madvise(DISCARD) should do what I was
> hoping for. (BTW, none of this has been tested with database stuff -
> I am just concentrating on reasonable extensions.
> 
> Here is the version of patch under test. 
> (Darren - I am sending this out without your permission, I hope
> you are okay with it).
>  

Of course, no problem.  I have a separate patch for sles9sp2 if that is of 
interest.  Please keep me in the loop with any feedback on the patch.

-- 
Darren Hart
IBM Linux Technology Center
Linux Kernel Team
Phone: 503 578 3185
   T/L: 775 3185

--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-10-19 19:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 17:30 [RFC] " Badari Pulavarty
2005-10-17 18:13 ` Hugh Dickins
2005-10-17 18:25   ` Hugh Dickins
2005-10-17 23:14     ` Badari Pulavarty
2005-10-18 16:05     ` [RFC][PATCH] " Badari Pulavarty
2005-10-19 17:56       ` Hugh Dickins
2005-10-19 18:32         ` Jeff Dike
2005-10-19 21:21           ` Badari Pulavarty
2005-10-19 22:38             ` Jeff Dike
2005-10-19 18:50         ` Badari Pulavarty
2005-10-19 19:12           ` Darren Hart [this message]
2005-10-19 20:10           ` Hugh Dickins
2005-10-19 20:47           ` Jeff Dike
2005-10-20 15:11             ` Badari Pulavarty
2005-10-20 17:27               ` Jeff Dike
2005-10-20 22:37                 ` Badari Pulavarty
2005-10-24 20:04                   ` Hugh Dickins
2005-10-24 20:22                     ` Darren Hart
2005-10-24 20:24                     ` Badari Pulavarty

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=43569A8F.4040300@us.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=chrisw@osdl.org \
    --cc=hugh@veritas.com \
    --cc=jdike@addtoit.com \
    --cc=linux-mm@kvack.org \
    --cc=pbadari@us.ibm.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