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-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org, corbet@lwn.net,
akpm@linux-foundation.org, honggyu.kim@sk.com, rakie.kim@sk.com,
hyeongtak.ji@sk.com, mhocko@kernel.org, vtavarespetr@micron.com,
jgroves@micron.com, ravis.opensrc@micron.com,
sthanneeru@micron.com, emirakhur@micron.com, Hasan.Maruf@amd.com,
seungjun.ha@samsung.com, hannes@cmpxchg.org,
dan.j.williams@intel.com,
Srinivasulu Thanneeru <sthanneeru.opensrc@micron.com>
Subject: Re: [PATCH v4 3/3] mm/mempolicy: introduce MPOL_WEIGHTED_INTERLEAVE for weighted interleaving
Date: Wed, 31 Jan 2024 21:01:07 -0500 [thread overview]
Message-ID: <Zbr7YzjFrrIWXomI@memverge.com> (raw)
In-Reply-To: <871q9xeyo4.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Thu, Feb 01, 2024 at 09:55:07AM +0800, Huang, Ying wrote:
> > diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> > index b1437396c357..dfd097009606 100644
> > --- a/mm/mempolicy.c
> > +++ b/mm/mempolicy.c
> > @@ -2391,7 +2391,7 @@ static unsigned long alloc_pages_bulk_array_weighted_interleave(gfp_t gfp,
> > unsigned long nr_allocated = 0;
> > unsigned long rounds;
> > unsigned long node_pages, delta;
> > - u8 __rcu *table, *weights, weight;
> > + u8 __rcu *table, __rcu *weights, weight;
>
> The __rcu usage can be checked with `sparse` directly. For example,
>
> make C=1 mm/mempolicy.o
>
> More details can be found in
>
> https://www.kernel.org/doc/html/latest/dev-tools/sparse.html
>
> Per my understanding, we shouldn't use "__rcu" here. Please search
> "__rcu" in the following document.
>
> https://www.kernel.org/doc/html/latest/RCU/checklist.html
>
Thanks for this, I will sort this out and respond here with changes
before v5.
> > @@ -2460,17 +2454,10 @@ static unsigned long alloc_pages_bulk_array_weighted_interleave(gfp_t gfp,
> > node_pages += weight;
> > delta -= weight;
> > } else if (delta) {
> > + /* when delta is deleted, resume from that node */
> ~~~~~~~
> depleted?
ack.
> > +retry:
> > + /* to prevent miscount use tsk->mems_allowed_seq to detect rebind */
> > + cpuset_mems_cookie = read_mems_allowed_begin();
> > if (!current->il_weight || !node_isset(node, policy->nodes)) {
> > node = next_node_in(node, policy->nodes);
>
> node will be changed in the loop. So we need to change the logic here.
>
Good catch, stupid mistake. ack.
> > @@ -2388,10 +2401,17 @@ static unsigned long alloc_pages_bulk_array_weighted_interleave(gfp_t gfp,
> > int prev_node;
> > int i;
> >
> > +
>
> Change by accident?
>
ack.
~Gregory
next prev parent reply other threads:[~2024-02-01 2:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 18:20 [PATCH v4 0/3] mm/mempolicy: weighted interleave mempolicy and sysfs extension Gregory Price
2024-01-30 18:20 ` [PATCH v4 1/3] mm/mempolicy: implement the sysfs-based weighted_interleave interface Gregory Price
2024-01-30 18:20 ` [PATCH v4 2/3] mm/mempolicy: refactor a read-once mechanism into a function for re-use Gregory Price
2024-01-30 18:20 ` [PATCH v4 3/3] mm/mempolicy: introduce MPOL_WEIGHTED_INTERLEAVE for weighted interleaving Gregory Price
2024-01-31 5:12 ` Gregory Price
2024-01-31 6:43 ` Huang, Ying
2024-01-31 7:43 ` Gregory Price
2024-01-31 9:19 ` Huang, Ying
2024-01-31 16:35 ` Gregory Price
2024-01-31 17:29 ` Gregory Price
2024-02-01 1:55 ` Huang, Ying
2024-02-01 2:01 ` Gregory Price [this message]
2024-02-01 2:18 ` Gregory Price
2024-02-01 3:02 ` Huang, Ying
2024-02-01 3:10 ` Gregory Price
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=Zbr7YzjFrrIWXomI@memverge.com \
--to=gregory.price@memverge.com \
--cc=Hasan.Maruf@amd.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=emirakhur@micron.com \
--cc=gourry.memverge@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=honggyu.kim@sk.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=mhocko@kernel.org \
--cc=rakie.kim@sk.com \
--cc=ravis.opensrc@micron.com \
--cc=seungjun.ha@samsung.com \
--cc=sthanneeru.opensrc@micron.com \
--cc=sthanneeru@micron.com \
--cc=vtavarespetr@micron.com \
--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