From: Vlastimil Babka <vbabka@suse.cz>
To: Faiyaz Mohammed <faiyazm@codeaurora.org>,
cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, greg@kroah.com,
glittao@gmail.com, andy.shevchenko@gmail.com
Cc: vinmenon@codeaurora.org
Subject: Re: [PATCH v11] mm: slub: move sysfs slab alloc/free interfaces to debugfs
Date: Tue, 8 Jun 2021 11:41:46 +0200 [thread overview]
Message-ID: <d79ff9cd-e72d-0e6a-1fb0-e8a64b20138a@suse.cz> (raw)
In-Reply-To: <1623141934-7699-1-git-send-email-faiyazm@codeaurora.org>
On 6/8/21 10:45 AM, Faiyaz Mohammed wrote:
> alloc_calls and free_calls implementation in sysfs have two issues,
> one is PAGE_SIZE limitation of sysfs and other is it does not adhere
> to "one value per file" rule.
>
> To overcome this issues, move the alloc_calls and free_calls
> implementation to debugfs.
>
> Debugfs cache will be created if SLAB_STORE_USER flag is set.
>
> Rename the alloc_calls/free_calls to alloc_traces/free_traces,
> to be inline with what it does.
>
> Signed-off-by: Faiyaz Mohammed <faiyazm@codeaurora.org>
Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
Thanks!
next prev parent reply other threads:[~2021-06-08 9:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 8:45 Faiyaz Mohammed
2021-06-08 9:41 ` Vlastimil Babka [this message]
2021-06-08 11:50 ` Andy Shevchenko
2021-06-08 17:11 ` Faiyaz Mohammed
2021-06-08 17:35 ` Vlastimil Babka
2021-06-08 18:13 ` Faiyaz Mohammed
2021-06-10 8:56 ` Faiyaz Mohammed
2021-06-10 10:16 ` Andy Shevchenko
2021-06-10 10:18 ` Vlastimil Babka
-- strict thread matches above, loose matches on Subject: below --
2021-06-08 1:32 Faiyaz Mohammed
2021-06-08 7:28 ` kernel test robot
2021-06-08 7:35 ` Faiyaz Mohammed
2021-06-08 13:19 ` kernel test robot
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=d79ff9cd-e72d-0e6a-1fb0-e8a64b20138a@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=cl@linux.com \
--cc=faiyazm@codeaurora.org \
--cc=glittao@gmail.com \
--cc=greg@kroah.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vinmenon@codeaurora.org \
/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