From: Atish Patra <atish.patra@wdc.com> To: linux-kernel@vger.kernel.org Cc: Atish Patra <atish.patra@wdc.com>, Albert Ou <aou@eecs.berkeley.edu>, linux-riscv@lists.infradead.org, Palmer Dabbelt <palmer@sifive.com>, Paul Walmsley <paul.walmsley@sifive.com>, Christoph Hellwig <hch@lst.de>, Anup Patel <Anup.Patel@wdc.com> Subject: [PATCH v4 0/3] Optimize tlbflush path Date: Thu, 22 Aug 2019 00:51:48 -0700 [thread overview] Message-ID: <20190822075151.24838-1-atish.patra@wdc.com> (raw) This series adds few optimizations to reduce the trap cost in the tlb flush path. We should only make SBI calls to remote tlb flush only if absolutely required. This series is based on Christoph's series: http://lists.infradead.org/pipermail/linux-riscv/2019-August/006148.html Changes from v3->v4 1. Simplify the local vs remote usecase. 2. Reorder the patches in the series. Changes from v2->v3: 1. Split the patches into smaller one per optimization. Atish Patra (3): RISC-V: Do not invoke SBI call if cpumask is empty RISC-V: Issue a local tlbflush if possible. RISC-V: Issue a tlb page flush if possible arch/riscv/mm/tlbflush.c | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) -- 2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Atish Patra <atish.patra@wdc.com> To: linux-kernel@vger.kernel.org Cc: Albert Ou <aou@eecs.berkeley.edu>, Palmer Dabbelt <palmer@sifive.com>, Atish Patra <atish.patra@wdc.com>, Anup Patel <Anup.Patel@wdc.com>, Paul Walmsley <paul.walmsley@sifive.com>, linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de> Subject: [PATCH v4 0/3] Optimize tlbflush path Date: Thu, 22 Aug 2019 00:51:48 -0700 [thread overview] Message-ID: <20190822075151.24838-1-atish.patra@wdc.com> (raw) This series adds few optimizations to reduce the trap cost in the tlb flush path. We should only make SBI calls to remote tlb flush only if absolutely required. This series is based on Christoph's series: http://lists.infradead.org/pipermail/linux-riscv/2019-August/006148.html Changes from v3->v4 1. Simplify the local vs remote usecase. 2. Reorder the patches in the series. Changes from v2->v3: 1. Split the patches into smaller one per optimization. Atish Patra (3): RISC-V: Do not invoke SBI call if cpumask is empty RISC-V: Issue a local tlbflush if possible. RISC-V: Issue a tlb page flush if possible arch/riscv/mm/tlbflush.c | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) -- 2.21.0 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-08-22 7:59 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-22 7:51 Atish Patra [this message] 2019-08-22 7:51 ` [PATCH v4 0/3] Optimize tlbflush path Atish Patra 2019-08-22 7:51 ` [PATCH v4 1/3] RISC-V: Do not invoke SBI call if cpumask is empty Atish Patra 2019-08-22 7:51 ` Atish Patra 2019-08-22 8:10 ` Christoph Hellwig 2019-08-22 8:10 ` Christoph Hellwig 2019-08-22 7:51 ` [PATCH v4 2/3] RISC-V: Issue a local tlbflush if possible Atish Patra 2019-08-22 7:51 ` Atish Patra 2019-08-22 8:10 ` Christoph Hellwig 2019-08-22 8:10 ` Christoph Hellwig 2019-08-22 7:51 ` [PATCH v4 3/3] RISC-V: Issue a tlb page flush " Atish Patra 2019-08-22 7:51 ` Atish Patra 2019-08-22 8:11 ` Christoph Hellwig 2019-08-22 8:11 ` Christoph Hellwig 2019-08-22 18:31 ` Atish Patra 2019-08-22 18:31 ` Atish Patra 2019-08-31 2:50 ` [PATCH v4 0/3] Optimize tlbflush path Paul Walmsley 2019-08-31 2:50 ` Paul Walmsley 2019-09-28 4:23 ` Atish Patra 2019-09-28 4:23 ` Atish Patra 2019-10-25 3:09 ` Paul Walmsley 2019-10-25 3:09 ` Paul Walmsley 2019-10-31 15:13 ` Atish Patra 2019-10-31 15:13 ` Atish Patra
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=20190822075151.24838-1-atish.patra@wdc.com \ --to=atish.patra@wdc.com \ --cc=Anup.Patel@wdc.com \ --cc=aou@eecs.berkeley.edu \ --cc=hch@lst.de \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@sifive.com \ --cc=paul.walmsley@sifive.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: linkBe 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.