public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Shashi Kiran T.R." <Shashi.Kiran@wipro.com>
To: linux-kernel@vger.kernel.org, Shashi.Kiran@wipro.com
Subject: Kernel memory mapped into user process
Date: Wed, 23 May 2001 11:35:47 +0530	[thread overview]
Message-ID: <3B0B533B.B902EE85@wipro.tcpn.com> (raw)

Hi ,

    I have a proposition at hand to optimize getting system time by
avoiding
the system call(gettimeofday()) overhead. This can be implemented by
keeping a read-only page of kernel memory mapped into user processes
for reading quickly. A kernel process can keep that page up-to-date.

   I did some browsing of this mailing list archives to get the
following related
topics:
*  mapping user space buffer to kernel address space
* Direct I/O
* Zero Copy IO
  None of these seem to specifically address my problem.

So can the experienced please throw some light on the issues involved
in having a read-only page of kernel memory mapped into user process.
Any help/suggestions will be much appreciated. Please CC your comments
to "trsk@wipro.tcpn.com"

Thanks and Regards,
  Shashi


                 reply	other threads:[~2001-05-23  6:01 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=3B0B533B.B902EE85@wipro.tcpn.com \
    --to=shashi.kiran@wipro.com \
    --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