From: Pete Zaitcev <zaitcev@redhat.com>
To: "Tillier, Fabian" <ftillier@infiniconsys.com>
Cc: linux-kernel@vger.kernel.org, zaitcev@redhat.com,
sean.hefty@intel.com, linux-kernel@vger.kernel.org,
woody@co.intel.com, woody@jf.intel.com
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in theLinux kernel
Date: Sun, 8 Feb 2004 17:51:07 -0800 [thread overview]
Message-ID: <20040208175107.08b84865.zaitcev@redhat.com> (raw)
In-Reply-To: <mailman.1076018705.12618.linux-kernel2news@redhat.com>
On Thu, 5 Feb 2004 17:02:30 -0500
"Tillier, Fabian" <ftillier@infiniconsys.com> wrote:
> That is absolutely correct. In addition to portability between kernel
> versions and operating systems, there is also portability between
> user-mode and kernel-mode within a single release.
Just for the record, Robert and Asok visited OLS in 2002 and I seem to
recall explaining to them in excuriating detail why an exact compatibility
between user mode and kernel mode API was a crock of shit, pipe dream,
etc. etc., at least in the context of Linux. Failed to make a dent,
apparently. But at least I tried!
On the other hand, I ate Asok's brain about callbacks until he caved,
so it's not all hopeless. Intel people are competent, they just come from
a different cultural background. I think that instead of plonking it would
be more productive to explain them the issues, e.g. the cost of insane
and atrocious abstractions they have in the stack, that ia64 is not the
only 64 bit architecture in the world (no matter how much Intel wants us
to believe it), that IOMMUs actually exist (in HP's Itanic servers, for
one), such kind of thing.
-- Pete
next parent reply other threads:[~2004-02-09 1:51 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1076018705.12618.linux-kernel2news@redhat.com>
2004-02-09 1:51 ` Pete Zaitcev [this message]
2004-02-24 17:55 Woodruff, Robert J
2004-02-24 18:03 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-02-08 23:43 Arnd Bergmann
2004-02-08 21:36 Woodruff, Robert J
2004-02-06 16:42 Hefty, Sean
2004-02-06 17:05 ` Richard B. Johnson
2004-02-06 17:23 ` Roland Dreier
2004-02-06 18:00 ` Richard B. Johnson
2004-02-06 18:12 ` Måns Rullgård
2004-02-06 18:13 ` Chris Friesen
2004-02-06 18:22 ` Valdis.Kletnieks
2004-02-06 18:50 ` Richard B. Johnson
2004-02-06 19:02 ` Matti Aarnio
2004-02-06 19:11 ` Petr Vandrovec
2004-02-07 3:05 ` Jamie Lokier
2004-02-06 18:54 ` Måns Rullgård
2004-02-06 19:01 ` somenath
2004-02-06 17:27 ` Troy Benjegerdes
2004-02-06 18:51 ` Greg KH
2004-02-08 8:31 ` Fab Tillier
2004-02-08 16:29 ` Greg KH
2004-02-08 16:51 ` Fab Tillier
2004-02-09 2:55 ` Troy Benjegerdes
2004-02-09 2:57 ` Greg KH
2004-02-06 4:07 Perez-Gonzalez, Inaky
2004-02-05 23:09 Woodruff, Robert J
2004-02-05 22:55 Woodruff, Robert J
2004-02-05 22:54 ` Randy.Dunlap
2004-02-05 22:26 Hefty, Sean
2004-02-05 22:40 ` Christoph Hellwig
2004-02-05 22:39 ` Randy.Dunlap
2004-02-05 23:19 ` Greg KH
2004-02-06 1:10 ` Troy Benjegerdes
2004-02-05 22:17 Tillier, Fabian
2004-02-05 22:56 ` Brian Gerst
2004-02-05 22:58 ` Bernd Petrovitsch
2004-02-05 22:02 Tillier, Fabian
2004-02-06 1:57 ` Troy Benjegerdes
2004-02-05 20:32 Tillier, Fabian
2004-02-05 21:27 ` Greg KH
2004-02-05 21:56 ` Chris Friesen
2004-02-06 20:22 ` Bill Davidsen
2004-02-05 19:26 Tillier, Fabian
2004-02-05 20:27 ` Greg KH
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=20040208175107.08b84865.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=ftillier@infiniconsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.hefty@intel.com \
--cc=woody@co.intel.com \
--cc=woody@jf.intel.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
all inboxes | Powered by JetHome®