From: Paul Jackson <pj@sgi.com>
To: Dave Peterson <dsp@llnl.gov>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
riel@surriel.com, nickpiggin@yahoo.com.au, ak@suse.de,
akpm@osdl.org
Subject: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
Date: Thu, 27 Apr 2006 13:44:42 -0700 [thread overview]
Message-ID: <20060427134442.639a6d19.pj@sgi.com> (raw)
In-Reply-To: <200604271308.10080.dsp@llnl.gov>
Dave wrote:
> @@ -350,6 +353,8 @@ struct mm_struct {
> /* aio bits */
> rwlock_t ioctx_list_lock;
> struct kioctx *ioctx_list;
> +
> + unsigned long flags;
I see Andi didn't reply to your question concerning what
struct he saw a 'flags' in.
Adding a flags word still costs a slot in mm_struct.
Adding a 'oom_notify' bitfield after the existing 'dumpable'
bitfield in mm_struct would save that slot:
unsigned dumpable:2;
unsigned oom_notify:1;
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
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>
next prev parent reply other threads:[~2006-04-27 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 20:08 [PATCH 1/2 (repost)] mm: serialize OOM kill operations Dave Peterson
2006-04-27 20:44 ` Paul Jackson [this message]
2006-04-27 21:09 ` Andrew Morton
2006-04-27 21:32 ` Dave Peterson
2006-04-27 23:02 ` Paul Jackson
2006-04-28 22:09 ` Dave Peterson
2006-04-27 22:56 ` Andrew Morton
2006-04-28 21:59 ` Dave Peterson
2006-04-28 22:16 ` Andrew Morton
2006-04-28 22:24 ` Dave Peterson
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=20060427134442.639a6d19.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dsp@llnl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@surriel.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;
as well as URLs for NNTP newsgroup(s).