mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: anand@eis.iisc.ernet.in (SVR Anand)
To: linux-kernel@vger.kernel.org
Subject: Buffer copying latency
Date: Thu, 9 Nov 2000 19:10:42 +0530 (GMT+05:30)	[thread overview]
Message-ID: <200011091340.TAA05912@eis.iisc.ernet.in> (raw)

Hi,

Sorry if it is a naive question.

I would like to know if there are any measurements made on a typical Pentium
machine with respect to the latency for buffer copying from the user to kernel 
and vice versa. While there are many papers, and arguments that attempt to
ban buffering copying of any sort, especially the ones that cross protection
boubdaries, I am searching in vain to obtain the numbers that highlight the 
overheads. Can you help me getting this information ?


It also causes a bit of worry that the recent trends seem to violate the nice
conventional Unix philosophy in the name of performance,... just because the
current RAM access speeds are not upto the mark. What would happen if some
technology breakthrough occurs and the RAM access times fall drastically ?

Regards
Anand
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-11-09 13:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200011091340.TAA05912@eis.iisc.ernet.in \
    --to=anand@eis.iisc.ernet.in \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®