From: Jay Lan <jlan@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
csa@oss.sgi.com, akpm@osdl.org, guillaume.thouvenin@bull.net,
tim@physik3.uni-rostock.de, corliss@digitalmages.com
Subject: Re: [Lse-tech] Re: [PATCH 2.6.9-rc2 2/2] enhanced MM accounting data collection
Date: Fri, 01 Oct 2004 17:38:38 -0700 [thread overview]
Message-ID: <415DF88E.4020002@sgi.com> (raw)
In-Reply-To: <20040928023350.611c84d8.pj@sgi.com>
Paul Jackson wrote:
> nits:
>
> 1) I'm not sure the "no-op if CONFIG_CSA not set" comments
> are worthwhile - it does not seem to be a common practice
> to mark macros that collapse under certain CONFIG's with
> such comments, and some code, such as in fork.c, would
> become quite a bit less readable if such comments were
> widely used.
Yeah, that makes sense. Will be fixed in next posting.
>
> 2) Three of the added csa_update_integrals() lines have
> leading spaces, instead of a tab char, such as in:
>
> ===================================================================
> --- linux.orig/fs/exec.c 2004-09-27 11:57:40.201435722 -0700
> +++ linux/fs/exec.c 2004-09-27 14:05:41.266160725 -0700
> @@ -1163,6 +1164,9 @@
>
> /* execve success */
> security_bprm_free(&bprm);
> + /* no-op if CONFIG_CSA not set */
> + csa_update_integrals(); <=========
> + update_mem_hiwater(); <=========
> return retval;
> }
Caused by 'cut-n-paste'. Will be fixed.
>
> 3) Is it always the case that csa_update_integrals() and
> update_mem_hiwater() are used together? If so, perhaps
> they could be collapsed into one? Even the current->mm
> test inside them could be made one test, perhaps?
As Robin pointed out, there are a couple of instances that are
not the case. Actually there are three.
Thanks for your feedback, Paul!
- jay
prev parent reply other threads:[~2004-10-02 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 22:34 [PATCH 2.6.9-rc2 0/2] enhanced accounting data collection Jay Lan
2004-09-27 22:44 ` [PATCH 2.6.9-rc2 1/2] enhanced I/O " Jay Lan
2004-09-27 22:50 ` [PATCH 2.6.9-rc2 2/2] enhanced MM " Jay Lan
2004-09-28 9:33 ` Paul Jackson
2004-09-28 11:38 ` Robin Holt
2004-09-28 13:29 ` Paul Jackson
2004-09-28 14:34 ` Robin Holt
2004-10-02 0:38 ` Jay Lan [this message]
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=415DF88E.4020002@sgi.com \
--to=jlan@sgi.com \
--cc=akpm@osdl.org \
--cc=corliss@digitalmages.com \
--cc=csa@oss.sgi.com \
--cc=guillaume.thouvenin@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=pj@sgi.com \
--cc=tim@physik3.uni-rostock.de \
/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