From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Question about memcpy
Date: Tue, 10 Jul 2018 08:22:59 +0200 [thread overview]
Message-ID: <20180710062259.GA341@kroah.com> (raw)
In-Reply-To: <CACdNawon6L5oJb-EXqq-_J4gYkySw7+EhhyzurN-s4zAmqf=1Q@mail.gmail.com>
On Tue, Jul 10, 2018 at 12:50:21PM +0800, bing zhu wrote:
> I agree !,just i think the problem is still there,memcpy is indeed faster in
> kernel than in user,i've tried both ways .
Make sure you are actually using the same code for memcpy in both
places. Do not rely on your libc or the kernel library for such a
thing, otherwise you are not comparing the same code exactly.
> schedule might be to blame.
Lots of things "might be to blame", but first off, try to work out
exactly what you are trying to test, and why, and work on that.
good luck!
greg k-h
next prev parent reply other threads:[~2018-07-10 6:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 11:36 Question about memcpy bing zhu
2018-07-07 18:44 ` valdis.kletnieks at vt.edu
2018-07-08 14:03 ` bing zhu
2018-07-09 7:54 ` 袁建鹏
2018-07-09 8:14 ` bing zhu
2018-07-09 14:04 ` Himanshu Jha
2018-07-09 16:16 ` valdis.kletnieks at vt.edu
2018-07-14 10:10 ` Himanshu Jha
2018-07-10 4:50 ` bing zhu
2018-07-10 6:22 ` Greg KH [this message]
2018-07-10 14:51 ` bing zhu
2018-07-10 14:57 ` Greg KH
2018-07-10 16:03 ` valdis.kletnieks at vt.edu
2018-07-12 4:47 ` bing zhu
2018-07-12 5:34 ` Greg KH
2018-07-12 14:27 ` bing zhu
2018-07-12 14:53 ` Greg KH
2018-07-13 3:02 ` bing zhu
2018-07-13 7:33 ` valdis.kletnieks at vt.edu
2018-07-17 2:44 ` bing zhu
2018-07-12 16:49 ` valdis.kletnieks at vt.edu
-- strict thread matches above, loose matches on Subject: below --
2018-07-07 13:21 Alex Arvelaez
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=20180710062259.GA341@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).