public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Pedretti <ktpedre@sandia.gov>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: do_exit() and lock_kernel() semantics
Date: Mon, 25 Mar 2002 12:46:13 -0800	[thread overview]
Message-ID: <3C9F8C95.8090506@sandia.gov> (raw)
In-Reply-To: <003301c1d439$97a26030$010411ac@local>

Manfred Spraul wrote:

>>Thus, for each receive we have to convert the virt address of the
>>user-land receive buffer to a physical address (in the kernel region)
>>before doing the memcpy (copy_to_user doesn't work from interrupt
>>context).
>>
>
>Why do you want to do that at interrupt time?
>I'd call map_user_kiobuf() when the user-land buffer is set up, and then
>write directly (i.e. with kmap_atomic()) into the pages stored in
>iobuf->maplist[]. It avoids the page table scan at interrupt time.
>
>Which platform do you use? map_user_kiobuf() doesn't enforce cache
>coherency internally, outside of i386 you might need additional
>flush_cache_whatever (see Documentation/cachetlb.txt)
>
>--
>    Manfred
>

I'm guessing the reason is that this module was initially developed on 
2.0 and ported to 2.2. and 2.4.  I think the kiobuf stuff is only in 
2.4+, right?  I should probably work on converting things, although our 
production Cplant cluster is still using 2.2.  It might help reduce our 
latency, although I'm guessing the page table walk is pretty quick.

This module needs to work on Alpha, i386, and ia64 so I'd have to look 
into the cache issues.

Thanks,
Kevin  


  reply	other threads:[~2002-03-26  0:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 20:13 do_exit() and lock_kernel() semantics Manfred Spraul
2002-03-25 20:46 ` Kevin Pedretti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-25 19:25 Kevin Pedretti
2002-03-25 20:17 ` Andrew Morton
2002-03-26  7:53 ` Ashok Raj
2002-03-26 10:11 ` Itai Nahshon

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=3C9F8C95.8090506@sandia.gov \
    --to=ktpedre@sandia.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /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