All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, dancol@google.com, vbabka@suse.cz
Subject: Re: + mm-proc-pid-smaps_rollup-convert-to-single-value-seq_file.patch added to -mm tree
Date: Tue, 24 Jul 2018 21:29:08 +0300	[thread overview]
Message-ID: <20180724182908.GD27053@avx2> (raw)
In-Reply-To: <20180723235548.nLTzP%akpm@linux-foundation.org>

On Mon, Jul 23, 2018 at 04:55:48PM -0700, akpm@linux-foundation.org wrote:
> The patch titled
>      Subject: mm: /proc/pid/smaps_rollup: convert to single value seq_file
> has been added to the -mm tree.  Its filename is
>      mm-proc-pid-smaps_rollup-convert-to-single-value-seq_file.patch

> Subject: mm: /proc/pid/smaps_rollup: convert to single value seq_file
> 
> The /proc/pid/smaps_rollup file is currently implemented via the
> m_start/m_next/m_stop seq_file iterators shared with the other maps files,
> that iterate over vma's.  However, the rollup file doesn't print anything
> for each vma, only accumulate the stats.

What I don't understand why keep seq_ops then and not do all the work in
->show hook.  Currently /proc/*/smaps_rollup is at ~500 bytes so with
minimum 1 page seq buffer, no buffer resizing is possible.

> +static int show_smaps_rollup(struct seq_file *m, void *v)
> +{
> +	struct proc_maps_private *priv = m->private;
> +	struct mem_size_stats *mss = priv->rollup;
> +	struct vm_area_struct *vma;
> +
> +	/*
> +	 * We might be called multiple times when e.g. the seq buffer
> +	 * overflows. Gather the stats only once.

It doesn't!

> +	if (!mss->finished) {
> +		for (vma = priv->mm->mmap; vma; vma = vma->vm_next) {
> +			smap_gather_stats(vma, mss);
> +			mss->last_vma_end = vma->vm_end;
>  		}
> -		last_vma = !m_next_vma(priv, vma);
> -	} else {
> -		rollup_mode = false;
> -		memset(&mss_stack, 0, sizeof(mss_stack));
> -		mss = &mss_stack;

           reply	other threads:[~2018-07-24 18:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20180723235548.nLTzP%akpm@linux-foundation.org>]

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=20180724182908.GD27053@avx2 \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dancol@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.