From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ingo Molnar <mingo@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Arjun Roy <arjunroy@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [PATCH v2 0/3] rseq: minor optimizations
Date: Tue, 13 Apr 2021 09:22:36 -0700 [thread overview]
Message-ID: <20210413162240.3131033-1-eric.dumazet@gmail.com> (raw)
From: Eric Dumazet <edumazet@google.com>
rseq is a heavy user of copy to/from user data in fast paths.
This series tries to reduce the cost.
v2: Addressed Peter and Mathieu feedbacks, thanks !
Eric Dumazet (3):
rseq: optimize rseq_update_cpu_id()
rseq: remove redundant access_ok()
rseq: optimise rseq_get_rseq_cs() and clear_rseq_cs()
kernel/rseq.c | 61 +++++++++++++++++++++++++++++++++++++--------------
1 file changed, 45 insertions(+), 16 deletions(-)
--
2.31.1.295.g9ea45b61b8-goog
next reply other threads:[~2021-04-13 16:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 16:22 Eric Dumazet [this message]
2021-04-13 16:22 ` [PATCH v2 1/3] rseq: optimize rseq_update_cpu_id() Eric Dumazet
2021-04-13 16:22 ` [PATCH v2 2/3] rseq: remove redundant access_ok() Eric Dumazet
2021-04-13 16:22 ` [PATCH v2 3/3] rseq: optimise rseq_get_rseq_cs() and clear_rseq_cs() Eric Dumazet
2021-04-13 16:54 ` Mathieu Desnoyers
2021-04-13 16:57 ` Eric Dumazet
2021-04-13 17:01 ` Eric Dumazet
2021-04-13 17:07 ` Eric Dumazet
2021-04-13 17:20 ` Mathieu Desnoyers
2021-04-13 17:33 ` Eric Dumazet
2021-04-13 18:00 ` Mathieu Desnoyers
2021-04-13 18:22 ` Eric Dumazet
2021-04-13 18:35 ` Arjun Roy
2021-04-13 21:19 ` David Laight
2021-04-13 22:03 ` Arjun Roy
2021-04-14 7:55 ` David Laight
2021-04-14 16:00 ` Eric Dumazet
2021-04-14 16:08 ` David Laight
2021-04-14 16:10 ` Eric Dumazet
2021-04-14 17:15 ` Arjun Roy
2021-04-14 17:35 ` Eric Dumazet
2021-04-14 20:15 ` Arjun Roy
2021-04-14 20:25 ` Eric Dumazet
2021-04-14 20:35 ` Arjun Roy
2021-04-13 19:13 ` Mathieu Desnoyers
2021-04-13 17:06 ` Mathieu Desnoyers
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=20210413162240.3131033-1-eric.dumazet@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=arjunroy@google.com \
--cc=boqun.feng@gmail.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
/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