linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Price <gregory.price@memverge.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Gregory Price <gourry.memverge@gmail.com>,
	linux-mm@kvack.org, linux-doc@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-api@vger.kernel.org, x86@kernel.org,
	akpm@linux-foundation.org, arnd@arndb.de, tglx@linutronix.de,
	luto@kernel.org, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com, mhocko@kernel.org,
	tj@kernel.org, corbet@lwn.net, rakie.kim@sk.com,
	hyeongtak.ji@sk.com, honggyu.kim@sk.com, vtavarespetr@micron.com,
	peterz@infradead.org, jgroves@micron.com,
	ravis.opensrc@micron.com, sthanneeru@micron.com,
	emirakhur@micron.com, Hasan.Maruf@amd.com,
	seungjun.ha@samsung.com
Subject: Re: [PATCH v4 11/11] mm/mempolicy: extend set_mempolicy2 and mbind2 to support weighted interleave
Date: Tue, 19 Dec 2023 13:12:56 -0500	[thread overview]
Message-ID: <ZYHdKLkvtDXjhoxS@memverge.com> (raw)
In-Reply-To: <87sf3ynb4x.fsf@yhuang6-desk2.ccr.corp.intel.com>

On Tue, Dec 19, 2023 at 11:07:10AM +0800, Huang, Ying wrote:
> Gregory Price <gourry.memverge@gmail.com> writes:
> 
> > diff --git a/include/uapi/linux/mempolicy.h b/include/uapi/linux/mempolicy.h
> > index ec1402dae35b..16fedf966166 100644
> > --- a/include/uapi/linux/mempolicy.h
> > +++ b/include/uapi/linux/mempolicy.h
> > @@ -33,6 +33,7 @@ struct mpol_args {
> >  	__u16 mode_flags;
> >  	__s32 home_node;	/* mbind2: policy home node */
> >  	__aligned_u64 pol_nodes;
> > +	__aligned_u64 il_weights; /* size: pol_maxnodes * sizeof(char) */
> >  	__u64 pol_maxnodes;
> >  	__s32 policy_node;	/* get_mempolicy: policy node info */
> >  };
> 
> You break the ABI you introduced earlier in the patchset.  Although they
> are done within a patchset, I don't think that it's a good idea.  I
> suggest to finalize the ABI in the first place.  Otherwise, people check
> git log will be confused by ABI broken.  This makes it easier to be
> reviewed too.
> 

This is a result of fixing alignment/holes (suggested by Arnd) and my
not dropping policy_node, which I'd originally planned to do.

I figured that whenever we decided to move forward, mempolicy2 and
mbind2 syscalls would end up squashed into a single commit for the
purpose of ensuring the feature goes in as a whole.  I can fix this
though.

~Gregory

  reply	other threads:[~2023-12-19 18:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 19:46 [PATCH v4 00/11] mempolicy2, mbind2, and weighted interleave Gregory Price
2023-12-18 19:46 ` [PATCH v4 01/11] mm/mempolicy: implement the sysfs-based weighted_interleave interface Gregory Price
2023-12-18 19:46 ` [PATCH v4 02/11] mm/mempolicy: introduce MPOL_WEIGHTED_INTERLEAVE for weighted interleaving Gregory Price
2023-12-18 19:46 ` [PATCH v4 03/11] mm/mempolicy: refactor sanitize_mpol_flags for reuse Gregory Price
2023-12-18 19:46 ` [PATCH v4 04/11] mm/mempolicy: create struct mempolicy_args for creating new mempolicies Gregory Price
2023-12-18 19:46 ` [PATCH v4 05/11] mm/mempolicy: refactor kernel_get_mempolicy for code re-use Gregory Price
2023-12-18 19:46 ` [PATCH v4 06/11] mm/mempolicy: allow home_node to be set by mpol_new Gregory Price
2023-12-18 19:46 ` [PATCH v4 07/11] mm/mempolicy: add userland mempolicy arg structure Gregory Price
2023-12-18 19:46 ` [PATCH v4 08/11] mm/mempolicy: add set_mempolicy2 syscall Gregory Price
2023-12-18 19:46 ` [PATCH v4 09/11] mm/mempolicy: add get_mempolicy2 syscall Gregory Price
2023-12-18 19:46 ` [PATCH v4 10/11] mm/mempolicy: add the mbind2 syscall Gregory Price
2023-12-19 12:24   ` kernel test robot
2023-12-20  0:48   ` kernel test robot
2023-12-18 19:46 ` [PATCH v4 11/11] mm/mempolicy: extend set_mempolicy2 and mbind2 to support weighted interleave Gregory Price
2023-12-19  3:07   ` Huang, Ying
2023-12-19 18:12     ` Gregory Price [this message]
2024-01-03 11:16   ` Dan Carpenter
2023-12-19  3:04 ` [PATCH v4 00/11] mempolicy2, mbind2, and " Huang, Ying
2023-12-19 18:09   ` Gregory Price
2023-12-20  2:27     ` Huang, Ying
2023-12-26  7:26       ` Gregory Price
2024-01-02  4:08         ` Huang, Ying

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=ZYHdKLkvtDXjhoxS@memverge.com \
    --to=gregory.price@memverge.com \
    --cc=Hasan.Maruf@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=emirakhur@micron.com \
    --cc=gourry.memverge@gmail.com \
    --cc=honggyu.kim@sk.com \
    --cc=hpa@zytor.com \
    --cc=hyeongtak.ji@sk.com \
    --cc=jgroves@micron.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rakie.kim@sk.com \
    --cc=ravis.opensrc@micron.com \
    --cc=seungjun.ha@samsung.com \
    --cc=sthanneeru@micron.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=vtavarespetr@micron.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.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).