From: David Hildenbrand <david@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, David Howells <dhowells@redhat.com>
Cc: John Hubbard <jhubbard@nvidia.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Jason Gunthorpe <jgg@nvidia.com>,
Logan Gunthorpe <logang@deltatee.com>,
Jeff Layton <jlayton@kernel.org>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] iov_iter: Improve page extraction (pin or just list)
Date: Tue, 31 Jan 2023 16:02:21 +0100 [thread overview]
Message-ID: <7f8f2d0f-4bf2-71aa-c356-c78c6b7fd071@redhat.com> (raw)
In-Reply-To: <f2fb6cc5-ff95-ca51-b377-5e4bd239d5e8@kernel.dk>
On 31.01.23 15:50, Jens Axboe wrote:
> On 1/31/23 6:48?AM, David Hildenbrand wrote:
>> On 31.01.23 14:41, David Howells wrote:
>>> David Hildenbrand <david@redhat.com> wrote:
>>>
>>>>>> percpu counters maybe - add them up at the point of viewing?
>>>>> They are percpu, see my last email. But for every 108 changes (on
>>>>> my system), they will do two atomic_long_adds(). So not very
>>>>> useful for anything but low frequency modifications.
>>>>>
>>>>
>>>> Can we just treat the whole acquired/released accounting as a debug mechanism
>>>> to detect missing releases and do it only for debug kernels?
>>>>
>>>>
>>>> The pcpu counter is an s8, so we have to flush on a regular basis and cannot
>>>> really defer it any longer ... but I'm curious if it would be of any help to
>>>> only have a single PINNED counter that goes into both directions (inc/dec on
>>>> pin/release), to reduce the flushing.
>>>>
>>>> Of course, once we pin/release more than ~108 pages in one go or we switch
>>>> CPUs frequently it won't be that much of a help ...
>>>
>>> What are the stats actually used for? Is it just debugging, or do we actually
>>> have users for them (control groups spring to mind)?
>>
>> As it's really just "how many pinning events" vs. "how many unpinning
>> events", I assume it's only for debugging.
>>
>> For example, if you pin the same page twice it would not get accounted
>> as "a single page is pinned".
>
> How about something like the below then? I can send it out as a real
> patch, will run a sanity check on it first but would be surprised if
> this doesn't fix it.
>
>
> diff --git a/mm/gup.c b/mm/gup.c
> index f45a3a5be53a..41abb16286ec 100644
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -168,7 +168,9 @@ struct folio *try_grab_folio(struct page *page, int refs, unsigned int flags)
> */
> smp_mb__after_atomic();
>
> +#ifdef CONFIG_DEBUG_VM
> node_stat_mod_folio(folio, NR_FOLL_PIN_ACQUIRED, refs);
> +#endif
>
> return folio;
> }
> @@ -180,7 +182,9 @@ struct folio *try_grab_folio(struct page *page, int refs, unsigned int flags)
> static void gup_put_folio(struct folio *folio, int refs, unsigned int flags)
> {
> if (flags & FOLL_PIN) {
> +#ifdef CONFIG_DEBUG_VM
> node_stat_mod_folio(folio, NR_FOLL_PIN_RELEASED, refs);
> +#endif
> if (folio_test_large(folio))
> atomic_sub(refs, folio_pincount_ptr(folio));
> else
> @@ -236,8 +240,9 @@ int __must_check try_grab_page(struct page *page, unsigned int flags)
> } else {
> folio_ref_add(folio, GUP_PIN_COUNTING_BIAS);
> }
> -
> +#ifdef CONFIG_DEBUG_VM
> node_stat_mod_folio(folio, NR_FOLL_PIN_ACQUIRED, 1);
> +#endif
> }
>
> return 0;
>
We might want to hide the counters completely by defining them only with
CONFIG_DEBUG_VM.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-01-31 15:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 11:14 David Howells
2023-01-30 21:33 ` Jens Axboe
2023-01-30 21:55 ` Jens Axboe
2023-01-30 21:57 ` Jens Axboe
2023-01-30 22:02 ` John Hubbard
2023-01-30 22:11 ` Jens Axboe
2023-01-30 22:12 ` David Howells
2023-01-30 22:15 ` Jens Axboe
2023-01-31 8:32 ` David Hildenbrand
2023-01-31 12:28 ` Jan Kara
2023-01-31 17:54 ` John Hubbard
2023-01-31 13:41 ` David Howells
2023-01-31 13:48 ` David Hildenbrand
2023-01-31 14:50 ` Jens Axboe
2023-01-31 15:02 ` David Hildenbrand [this message]
2023-01-31 15:04 ` Jens Axboe
2023-01-31 15:10 ` David Hildenbrand
2023-01-31 15:15 ` Jens Axboe
2023-01-30 21:52 ` David Howells
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=7f8f2d0f-4bf2-71aa-c356-c78c6b7fd071@redhat.com \
--to=david@redhat.com \
--cc=axboe@kernel.dk \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=jlayton@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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