All of lore.kernel.org
 help / color / mirror / Atom feed
From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: David Howells <dhowells@redhat.com>,
	"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
	Mateusz Guzik <mjguzik@gmail.com>,
	Neeraj Upadhyay <Neeraj.Upadhyay@amd.com>,
	Christian Brauner <brauner@kernel.org>,
	"Jeff Layton" <jlayton@kernel.org>,
	Oliver Sang <oliver.sang@intel.com>,
	"Swapnil Sapkal" <swapnil.sapkal@amd.com>,
	WangYuli <wangyuli@uniontech.com>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [PATCH v3 0/2] pipe: don't update {a,c,m}time for anonymous pipes
Date: Thu, 6 Feb 2025 08:42:12 +0530	[thread overview]
Message-ID: <28ed3e72-d219-4a02-aa8a-5b3ab413bc65@amd.com> (raw)
In-Reply-To: <20250205181716.GA13817@redhat.com>

Hello Oleg,

On 2/5/2025 11:47 PM, Oleg Nesterov wrote:
> OK, let me send v3 right now...

Tested this series with sched-messaging on my 3rd Generation EPYC
system (2 x64c/128T, boost on, C2 disabled) and I see slight
improvements:

   ==================================================================
   Test          : sched-messaging
   Units         : Normalized time in seconds
   Interpretation: Lower is better
   Statistic     : AMean
   ==================================================================
   Case:      upstream[pct imp](CV)    skip_{a,c,m}_time[pct imp](CV)
    1-groups     1.00 [ -0.00]( 9.88)     1.05 [ -5.16]( 7.19) *
    2-groups     1.00 [ -0.00]( 3.49)     0.97 [  2.70]( 3.54)
    4-groups     1.00 [ -0.00]( 1.22)     0.97 [  2.70]( 2.78)
    8-groups     1.00 [ -0.00]( 0.80)     0.99 [  0.94]( 1.04)
   16-groups     1.00 [ -0.00]( 1.40)     0.98 [  2.43]( 1.02)
   
   * Disregard these data points due to large run to run variation

Feel free to add:

Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>

I'll go test the pipe_{read,write}() cleanup you had posted on the
other thread.

-- 
Thanks and Regards,
Prateek

> 
> Changes: make pipeanon_fops static.
> 
> Link to v1: https://lore.kernel.org/all/20250204132153.GA20921@redhat.com/
> Link to v2: https://lore.kernel.org/all/20250205161636.GA1001@redhat.com/
> 
> Oleg.
> ---
> 
>   fs/pipe.c | 62 +++++++++++++++++++++++++++++++++++++++++++++++---------------
>   1 file changed, 47 insertions(+), 15 deletions(-)
> 


  parent reply	other threads:[~2025-02-06  3:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 18:17 [PATCH v3 0/2] pipe: don't update {a,c,m}time for anonymous pipes Oleg Nesterov
2025-02-05 18:17 ` [PATCH v3 1/2] pipe: introduce struct file_operations pipeanon_fops Oleg Nesterov
2025-02-05 18:18 ` [PATCH v3 2/2] pipe: don't update {a,c,m}time for anonymous pipes Oleg Nesterov
2025-02-06  3:12 ` K Prateek Nayak [this message]
2025-02-06  9:55 ` [PATCH v3 0/2] " Christian Brauner
2025-02-06 12:33 ` Jeff Layton

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=28ed3e72-d219-4a02-aa8a-5b3ab413bc65@amd.com \
    --to=kprateek.nayak@amd.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=gautham.shenoy@amd.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=oleg@redhat.com \
    --cc=oliver.sang@intel.com \
    --cc=swapnil.sapkal@amd.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wangyuli@uniontech.com \
    /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.