From: Matt Keenan <tank.en.mate@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
bgoglin@free.fr, addy@quadrics.com
Subject: Re: copy_one_pte()
Date: Thu, 15 Mar 2007 19:51:29 +0000 [thread overview]
Message-ID: <45F9A3C1.3000700@gmail.com> (raw)
In-Reply-To: <20070315110634.a2d08dce.akpm@linux-foundation.org>
Andrew Morton wrote:
> (cc restored. Please always do reply-to-all).
>
>
>> On Wed, 14 Mar 2007 08:35:07 +0000 Matt Keenan <tank.en.mate@gmail.com> wrote:
>> Christoph Hellwig wrote:
>>
>>> On Tue, Mar 13, 2007 at 08:15:25PM +0100, Zoltan Menyhart wrote:
>>>
>>>
>>>> I had a look at copy_one_pte().
>>>> I cannot see any ioproc_update_page() call, not even for the COW pages.
>>>> Is it intentional?
>>>>
>>>>
>>> There is no such thing as ioproc_update_page in any mainline tree.
>>> You must be looking at some vendor tree with braindead patches applied.
>>>
>>>
>>>
>> It looks like this function exists as a part of patches to support
>> Quadrics NICs / RDMA (HPC platforms). The patches are there so the
>> driver doesn't need to pin pages, it can be informed of page updates
>> directly. A patch was submitted to l-k sometime in 2005.
>>
>
> Oh Dear.
>
> Which vendor's kernel are we talking about here?
>
I don't know of any vendor's kernels that support this (but then I run
vanilla kernels on Debian). I just grep'ed for the patch because it
sounded interesting. There was a posting for it to l-k on 26th April
2005 from David Addison of Quadrics Ltd xref
http://lkml.org/lkml/2005/4/26/198 According to David, you (Andrew) and
Andrea Arcangeli asked for it to be posted for some feedback, the main
feedback was on whitespace issues and COWs w.r.t. fork(). Brice Goglin
made an interesting comment about using a similar method but tracking
VMAs rather than address spaces. By the looks of things it never went
into the mainline kernel. I lurk a bit (I sometimes miss things) on l-k
but I hadn't noticed any other methods for dynamic DMA direct to user
space (other than pinning pages), is there anything planned?
Matt
p.s. I Cc'ed Brice Goglin and David Addison
next prev parent reply other threads:[~2007-03-15 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 19:15 copy_one_pte() Zoltan Menyhart
2007-03-13 19:18 ` copy_one_pte() Christoph Hellwig
2007-03-14 8:35 ` copy_one_pte() Matt Keenan
2007-03-15 19:06 ` copy_one_pte() Andrew Morton
2007-03-15 19:51 ` Matt Keenan [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-02 16:17 copy_one_pte() Daniel J Blueman
[not found] ` <461209BE.6010905@bull.net>
2007-05-16 13:09 ` copy_one_pte() Daniel J Blueman
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=45F9A3C1.3000700@gmail.com \
--to=tank.en.mate@gmail.com \
--cc=addy@quadrics.com \
--cc=akpm@linux-foundation.org \
--cc=bgoglin@free.fr \
--cc=hch@lst.de \
--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