public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2/2 2.5.45 cleanup & add original copy_ro/from_user
Date: Sat, 2 Nov 2002 13:23:12 +0100	[thread overview]
Message-ID: <20021102132312.A563@wotan.suse.de> (raw)
In-Reply-To: <200211021216.gA2CGEp24534@Port.imtp.ilyichevsk.odessa.ua>

> It's easy to time memcpy() but harder to measure susequent
> cache misses when copied data gets accessed. We can read it
> back after memcpy and measure memcpy()+read, but is entire
> copy gets used immediately after memcpy() in real world usage?
> We're in benchmarking hell :(

You test common operations, like pipe bandwidth or ioctls.

-Andi

  reply	other threads:[~2002-11-02 12:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021102025838.220E.AT541@columbia.edu.suse.lists.linux.kernel>
     [not found] ` <3DC3A9C0.7979C276@digeo.com.suse.lists.linux.kernel>
2002-11-02 10:58   ` [PATCH] 2/2 2.5.45 cleanup & add original copy_ro/from_user Andi Kleen
2002-11-02 11:03     ` Andrew Morton
2002-11-02 16:55     ` Denis Vlasenko
2002-11-02 12:09       ` Andi Kleen
2002-11-02 17:08         ` Denis Vlasenko
2002-11-02 12:23           ` Andi Kleen [this message]
2002-11-04  3:36 Akira Tsukamoto
  -- strict thread matches above, loose matches on Subject: below --
2002-11-02  8:06 Akira Tsukamoto
2002-11-02 10:32 ` Andrew Morton
2002-11-02 11:07   ` Akira Tsukamoto
2002-11-02 18:13     ` Andrew Morton
2002-11-03  2:43       ` Akira Tsukamoto
2002-11-03  4:04         ` Andrew Morton
2002-11-03  2:43       ` Akira Tsukamoto
2002-11-03  2:57   ` Akira Tsukamoto
2002-11-03 21:24     ` Dave Jones
2002-11-03 22:22       ` Andries Brouwer

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=20021102132312.A563@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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