From: Andi Kleen <ak@muc.de>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Andrea Arcangeli <andrea@suse.de>,
David Addison <david.addison@quadrics.com>
Subject: Re: [PATCH][RFC] Linux VM hooks for advanced RDMA NICs
Date: Wed, 27 Apr 2005 15:43:58 +0200 [thread overview]
Message-ID: <m1hdhsxrkx.fsf@muc.de> (raw)
In-Reply-To: <426E751A.2020507@ens-lyon.org> (Brice Goglin's message of "Tue, 26 Apr 2005 19:06:34 +0200")
Brice Goglin <Brice.Goglin@ens-lyon.org> writes:
> I see two drawback in (2).
> First, it requires to play with the list of ioproc_ops when VMA are
> merged or split. Actually, it's not that bad since the list often
> contains only 1 ioproc_ops.
I had a similar problem with the NUMA policies. With some minor hacks
you could probably reuse the policy support by making it a weird kind
of policy. That would allow to keep the fast path impact very low,
which I think is the most important part of such hardware specific
narrow purpose, useless to 99.9999% of all users hacks
(Golden rule number 1 such code: dont impact anything else)
-Andi
next prev parent reply other threads:[~2005-04-27 13:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 15:49 [PATCH][RFC] Linux VM hooks for advanced RDMA NICs David Addison
2005-04-26 16:57 ` Jesper Juhl
2005-04-26 17:13 ` Lee Revell
2005-04-26 17:20 ` Jesper Juhl
2005-04-26 17:28 ` Lee Revell
2005-04-26 17:38 ` Jesper Juhl
2005-04-26 20:14 ` John W. Linville
2005-04-26 20:17 ` Lee Revell
2005-04-26 20:09 ` Lars Marowsky-Bree
2005-04-28 11:34 ` Jakob Oestergaard
2005-04-29 8:22 ` Benjamin Herrenschmidt
2005-04-26 17:06 ` Brice Goglin
2005-04-27 9:41 ` David Addison
2005-04-28 8:38 ` Andy Isaacson
2005-04-27 13:43 ` Andi Kleen [this message]
2005-04-28 1:42 ` Troy Benjegerdes
2005-04-28 7:21 ` Brice Goglin
2005-04-28 9:21 ` David Addison
2005-04-29 8:19 ` Benjamin Herrenschmidt
2005-04-29 9:25 ` David Addison
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=m1hdhsxrkx.fsf@muc.de \
--to=ak@muc.de \
--cc=Brice.Goglin@ens-lyon.org \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=david.addison@quadrics.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 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.