linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Kiryl Shutsemau <kirill@shutemov.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	linux-mm@kvack.org, Usama Arif <usamaarif642@gmail.com>
Subject: Re: [PATCH] tools/mm: Add madvise tool
Date: Fri, 5 Sep 2025 12:33:31 +0200	[thread overview]
Message-ID: <15e8b5a2-9b08-4f3b-b174-535eef6dadf1@redhat.com> (raw)
In-Reply-To: <zmueckzkhbfb2fgienlycsl7niedwvccqurlry3udfsjjw2lmq@6ujjt7oo2hzh>

On 05.09.25 12:24, Kiryl Shutsemau wrote:
> On Fri, Sep 05, 2025 at 12:19:11PM +0200, David Hildenbrand wrote:
>> On 04.09.25 19:57, kirill@shutemov.name wrote:
>>> From: Kiryl Shutsemau <kas@kernel.org>
>>>
>>> Add a simple tool that allows to issue an advice on a process or a file.
>>>
>>> It can be useful to experiment with effects of an advice on a workload
>>> without modifying the workload itself.
>>>
>>> Only supports advices available for process_madvise().
>>>
>>> Signed-off-by: Kiryl Shutsemau <kas@kernel.org>
>>> ---
>>
>>> +	if (pid) {
>>> +		struct iovec vec = {
>>> +			.iov_base = (void *)start,
>>> +			.iov_len = end - start,
>>> +		};
>>> +		ssize_t ret;
>>> +
>>> +		ret = process_madvise(fd, &vec, 1, advice, 0);
>>> +		if (ret < 0)
>>> +			perror("process_madvise"), exit(-1);
>>> +
>>> +		if ((unsigned long)ret != end - start)
>>> +			printf("Partial advice occurred. Stopped at %#lx\n", start + ret);
>>> +	} else {
>>> +		unsigned long addr, hpage_pmd_size;
>>> +		void *p;
>>> +		int ret;
>>> +
>>> +		hpage_pmd_size = read_pmd_pagesize();
>>> +		if (!hpage_pmd_size) {
>>> +			printf("Reading PMD pagesize failed");
>>> +			exit(-1);
>>> +		}
>>> +
>>> +		// Allocate virtual address space to align the target mmap to PMD size
>>> +		// Some advices require this.
>>
>> I assume the kernel coding-style applies to tools/ as well, so
>>
>> /*
>>   * ...
>>   */
> 
> I thought C99 comments are fine now, no? Like slab_common.c uses them.

Was there a recent discussion around that?

Coding style says "The preferred style for long (multi-line) comments is:"

slab_common.c seems to be the mostly the only thing in MM, for some 
weird reason (and it's even being inconsistent).

So please, just default to /* for MM stuff unless there is a pretty good 
reason not to.

-- 
Cheers

David / dhildenb



  reply	other threads:[~2025-09-05 10:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 17:57 kirill
2025-09-04 19:07 ` Liam R. Howlett
2025-09-05  3:26 ` wang lian
2025-09-05 10:28   ` Kiryl Shutsemau
2025-09-08  1:09     ` wang lian
2025-09-05  9:17 ` Michal Hocko
2025-09-05 10:16   ` Lorenzo Stoakes
2025-09-05 10:56     ` Michal Hocko
2025-09-05 11:02       ` Lorenzo Stoakes
2025-09-05 10:21   ` Kiryl Shutsemau
2025-09-05 11:02     ` Michal Hocko
2025-09-05 10:19 ` David Hildenbrand
2025-09-05 10:24   ` Kiryl Shutsemau
2025-09-05 10:33     ` David Hildenbrand [this message]
2025-09-05 10:35       ` Kiryl Shutsemau
2025-09-05 10:37 ` Lorenzo Stoakes
2025-09-05 13:35   ` Kiryl Shutsemau
2025-09-05 16:30   ` Kiryl Shutsemau
2025-09-05 10:45 ` Usama Arif
2025-09-05 10:59 ` Mike Rapoport
2025-09-05 13:36   ` Kiryl Shutsemau
2025-09-06  8:00     ` Mike Rapoport
2025-09-08 10:04       ` Kiryl Shutsemau
2025-09-10 11:34 ` [ANNOUNCE] mm-tools: Random tools MM-related tools Kiryl Shutsemau

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=15e8b5a2-9b08-4f3b-b174-535eef6dadf1@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=usamaarif642@gmail.com \
    --cc=vbabka@suse.cz \
    /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