mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nitin.m.gupta@oracle.com
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
	khalid.aziz@oracle.com, minchan@kernel.org,
	aneesh.kumar@linux.vnet.ibm.com, zhenzhang.zhang@huawei.com,
	sfr@canb.auug.org.au, mingo@kernel.org, chris.hyser@oracle.com,
	dahi@linux.vnet.ibm.com, toshi.kani@hpe.com, tony.luck@intel.com,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] sparc64: Reduce TLB flushes during hugepte changes
Date: Tue, 29 Mar 2016 19:41:05 -0400 (EDT)	[thread overview]
Message-ID: <20160329.194105.2209941679960771383.davem@davemloft.net> (raw)
In-Reply-To: <1459285913-141365-1-git-send-email-nitin.m.gupta@oracle.com>

From: Nitin Gupta <nitin.m.gupta@oracle.com>
Date: Tue, 29 Mar 2016 14:11:14 -0700

> During hugepage map/unmap, TSB and TLB flushes are currently
> issued at every PAGE_SIZE'd boundary which is unnecessary.
> We now issue the flush at REAL_HPAGE_SIZE boundaries only.
> 
> Without this patch workloads which unmap a large hugepage
> backed VMA region get CPU lockups due to excessive TLB
> flush calls.
> 
> Orabug: 22365539, 22643230, 22995196
> 
> Signed-off-by: Nitin Gupta <nitin.m.gupta@oracle.com>

You really need to put some more work into this, there are lots of
config variants you didn't even test.

See the kbuild robot replies...

      parent reply	other threads:[~2016-03-29 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 21:11 Nitin Gupta
2016-03-29 21:25 ` kbuild test robot
2016-03-29 22:38 ` kbuild test robot
2016-03-29 23:41 ` David Miller [this message]

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=20160329.194105.2209941679960771383.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=chris.hyser@oracle.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=khalid.aziz@oracle.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=mingo@kernel.org \
    --cc=nitin.m.gupta@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=toshi.kani@hpe.com \
    --cc=zhenzhang.zhang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®