LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Paul Jackson <pj@sgi.com>, Christoph Lameter <clameter@sgi.com>,
	Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
	Eric Whitney <eric.whitney@hp.com>
Subject: Re: Regression:  Re: [patch -mm 2/4] mempolicy: create mempolicy_operations structure
Date: Sat, 8 Mar 2008 14:09:11 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0803081403460.12095@chino.kir.corp.google.com> (raw)
In-Reply-To: <1205002171.4918.2.camel@localhost>

On Sat, 8 Mar 2008, Lee Schermerhorn wrote:

> > Excuse me, but there was significant discussion about this on LKML and I 
> > eventually did force MPOL_DEFAULT to require a non-empty nodemask 

Correction: s/non-empty/empty

> > specifically because of your demand that it should.  It didn't originally 
> > require this in my patchset, and now you're removing the exact same 
> > requirement that you demanded.
> > 
> > You said on February 13:
> > 
> > 	1) we've discussed the issue of returning EINVAL for non-empty
> > 	nodemasks with MPOL_DEFAULT.  By removing this restriction, we run
> > 	the risk of breaking applications if we should ever want to define
> > 	a semantic to non-empty node mask for MPOL_DEFAULT.
> > 
> > If you want to remove this requirement now (please get agreement from 
> > Paul) and are sure of your position, you'll at least need an update to 
> > Documentation/vm/numa-memory-policy.txt.
> 
> Excuse me.  I thought that the discussion--my position, anyway--was
> about preserving existing behavior for MPOL_DEFAULT which is to require
> an EMPTY [or NULL--same effect] nodemask.  Not a NON-EMPTY one.  See:
> http://www.kernel.org/doc/man-pages/online/pages/man2/set_mempolicy.2.html
> It does appear that your patches now require a non-empty nodemask.  This
> was intentional?
> 

The first and second set did not have this requirement, but the third set 
does (not currently in -mm), so I've changed it back.  Hopefully there's 
no confusion and we can settle on a solution without continuously 
revisiting the topic.

My position was originally to allow any type of nodemask to be passed with 
MPOL_DEFAULT since its not used.  You asked for strict argument checking 
and so after some debate I changed it to require an empty nodemask mainly 
because I didn't want the patchset to stall on such a minor point.  But in 
your regression fix, you expressed the desire once again to allow it to 
accept any nodemask because the testsuite does not check for it.

So if you'd like to do that, I'd encourage you to submit it as a separate 
patch and open it up for review.

What is currently in -mm and what I will be posting shortly is the updated 
regression fix.  All of these patches require that MPOL_DEFAULT include a 
NULL pointer or empty nodemask passed via the two syscalls.

> Note:  in the subject patch, I didn't enforce this behavior because your
> patch didn't [it enforced just the opposite], and I've pretty much given
> up.  Although I prefer current behavior [before your series], if we
> change it, we will need to change the man pages to remove the error
> condition for non-empty nodemasks with MPOL_DEFAULT.
> 

With my patches it still requires a NULL pointer or empty nodemask and 
I've updated Documentation/vm/numa_memory_policy.txt to explicitly say its 
an error if a non-empty nodemask is passed.

  reply	other threads:[~2008-03-08 22:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 20:05 [patch -mm 1/4] mempolicy: move rebind functions David Rientjes
2008-03-06 20:05 ` [patch -mm 2/4] mempolicy: create mempolicy_operations structure David Rientjes
2008-03-06 20:05   ` [patch -mm 3/4] mempolicy: small header file cleanup David Rientjes
2008-03-06 20:05     ` [patch -mm 4/4] mempolicy: remove includes for duplicate headers David Rientjes
2008-03-06 20:19       ` Paul Jackson
2008-03-06 20:51         ` David Rientjes
2008-03-06 21:01           ` Paul Jackson
2008-03-07  8:45             ` Andrew Morton
2008-03-07 20:44   ` Regression: Re: [patch -mm 2/4] mempolicy: create mempolicy_operations structure Lee Schermerhorn
2008-03-07 21:48     ` David Rientjes
2008-03-07 21:57       ` Paul Jackson
2008-03-08 18:49       ` Lee Schermerhorn
2008-03-08 22:09         ` David Rientjes [this message]
2008-03-10 14:58           ` Lee Schermerhorn
2008-03-12 19:33       ` [PATCH] Mempolicy: fix parsing of tmpfs mpol mount option Lee Schermerhorn

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=alpine.DEB.1.00.0803081403460.12095@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=eric.whitney@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.com \
    --subject='Re: Regression:  Re: [patch -mm 2/4] mempolicy: create mempolicy_operations structure' \
    /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

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).