From: Andrew Morton <akpm@linux-foundation.org>
To: Matt Keenan <tank.en.mate@gmail.com>
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: copy_one_pte()
Date: Thu, 15 Mar 2007 11:06:34 -0800 [thread overview]
Message-ID: <20070315110634.a2d08dce.akpm@linux-foundation.org> (raw)
In-Reply-To: <45F7B3BB.1030404@gmail.com>
(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?
next prev parent reply other threads:[~2007-03-15 19:06 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 ` Andrew Morton [this message]
2007-03-15 19:51 ` copy_one_pte() Matt Keenan
-- 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=20070315110634.a2d08dce.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tank.en.mate@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.