From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Vlastimil Babka <vbabka@suse•cz>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Waiman Long <longman@redhat•com>
Subject: Re: linux-next: manual merge of the akpm-current tree with the slab tree
Date: Fri, 17 Dec 2021 23:39:53 +1100 [thread overview]
Message-ID: <20211217233953.28062c5b@canb.auug.org.au> (raw)
In-Reply-To: <20211203181951.79618878@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 3412 bytes --]
Hi all,
On Fri, 3 Dec 2021 18:19:51 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> mm/memcontrol.c
>
> between commit:
>
> eefa12e18a92 ("mm/memcg: Convert slab objcgs from struct page to struct slab")
>
> from the slab tree and commit:
>
> 93e959c235eb ("mm/memcg: relocate mod_objcg_mlstate(), get_obj_stock() and put_obj_stock()")
>
> from the akpm-current tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> diff --cc mm/memcontrol.c
> index 522fff11d6d1,69d4fdafbb80..000000000000
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@@ -2816,10 -2769,63 +2769,63 @@@ retry
> */
> #define OBJCGS_CLEAR_MASK (__GFP_DMA | __GFP_RECLAIMABLE | __GFP_ACCOUNT)
>
> + /*
> + * Most kmem_cache_alloc() calls are from user context. The irq disable/enable
> + * sequence used in this case to access content from object stock is slow.
> + * To optimize for user context access, there are now two object stocks for
> + * task context and interrupt context access respectively.
> + *
> + * The task context object stock can be accessed by disabling preemption only
> + * which is cheap in non-preempt kernel. The interrupt context object stock
> + * can only be accessed after disabling interrupt. User context code can
> + * access interrupt object stock, but not vice versa.
> + */
> + static inline struct obj_stock *get_obj_stock(unsigned long *pflags)
> + {
> + struct memcg_stock_pcp *stock;
> +
> + if (likely(in_task())) {
> + *pflags = 0UL;
> + preempt_disable();
> + stock = this_cpu_ptr(&memcg_stock);
> + return &stock->task_obj;
> + }
> +
> + local_irq_save(*pflags);
> + stock = this_cpu_ptr(&memcg_stock);
> + return &stock->irq_obj;
> + }
> +
> + static inline void put_obj_stock(unsigned long flags)
> + {
> + if (likely(in_task()))
> + preempt_enable();
> + else
> + local_irq_restore(flags);
> + }
> +
> + /*
> + * mod_objcg_mlstate() may be called with irq enabled, so
> + * mod_memcg_lruvec_state() should be used.
> + */
> + static inline void mod_objcg_mlstate(struct obj_cgroup *objcg,
> + struct pglist_data *pgdat,
> + enum node_stat_item idx, int nr)
> + {
> + struct mem_cgroup *memcg;
> + struct lruvec *lruvec;
> +
> + rcu_read_lock();
> + memcg = obj_cgroup_memcg(objcg);
> + lruvec = mem_cgroup_lruvec(memcg, pgdat);
> + mod_memcg_lruvec_state(lruvec, idx, nr);
> + rcu_read_unlock();
> + }
> +
> -int memcg_alloc_page_obj_cgroups(struct page *page, struct kmem_cache *s,
> - gfp_t gfp, bool new_page)
> +int memcg_alloc_slab_cgroups(struct slab *slab, struct kmem_cache *s,
> + gfp_t gfp, bool new_slab)
> {
> - unsigned int objects = objs_per_slab_page(s, page);
> + unsigned int objects = objs_per_slab(s, slab);
> unsigned long memcg_data;
> void *vec;
>
This is now a conflict between the slab tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-17 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 7:19 linux-next: manual merge of the akpm-current tree with the slab tree Stephen Rothwell
2021-12-17 12:39 ` Stephen Rothwell [this message]
2021-12-21 0:10 ` Vlastimil Babka
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 7:22 Stephen Rothwell
2022-01-11 11:51 ` Stephen Rothwell
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=20211217233953.28062c5b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=longman@redhat$(echo .)com \
--cc=vbabka@suse$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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