All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Chun Ng <chunn@nvidia.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux Regressions <regressions@lists.linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Ankita Garg <ankitag@nvidia.com>
Subject: Re: [REGRESSION]: mmap performance regression starting with k-6.1
Date: Thu, 23 Nov 2023 12:01:20 +0700	[thread overview]
Message-ID: <ec120f27-e2de-4429-abf2-411d090e3316@gmail.com> (raw)
In-Reply-To: <PH7PR12MB79373516F591C102110B4251D6B9A@PH7PR12MB7937.namprd12.prod.outlook.com>

On 11/23/23 10:06, Chun Ng wrote:
>>> Did you mean that v6.0 doesn't have this regression?
> 
> No, k-6.0 does NOT have this regression. The regression starts from k-6.1.
> 

Thanks for confirmation.

-- 
An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2023-11-23  5:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 20:03 [REGRESSION]: mmap performance regression starting with k-6.1 Chun Ng
2023-11-23  1:18 ` Bagas Sanjaya
2023-11-23  3:06   ` Chun Ng
2023-11-23  5:01     ` Bagas Sanjaya [this message]
2023-11-23  5:07 ` Bagas Sanjaya
2023-11-23  8:29   ` David Wang
2023-11-23 14:34   ` Liam R. Howlett
2023-11-24  5:08     ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-26  7:18     ` David Wang
2023-11-26 13:47       ` Matthew Wilcox
2023-11-23 15:38   ` Matthew Wilcox
2023-11-24  0:15     ` Bagas Sanjaya
2023-11-24  1:04       ` Matthew Wilcox
2023-11-24 11:52         ` Greg KH
2023-11-24 15:06           ` Matthew Wilcox
2023-11-24 15:13             ` Greg KH
2023-11-24 15:29             ` Linux regression tracking (Thorsten Leemhuis)
2023-11-25  1:50               ` Chun Ng

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=ec120f27-e2de-4429-abf2-411d090e3316@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=ankitag@nvidia.com \
    --cc=chunn@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=regressions@lists.linux.dev \
    /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.