From: Troy Benjegerdes <hozer@hozed.org>
To: "Tillier, Fabian" <ftillier@infiniconsys.com>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
Greg KH <greg@kroah.com>, "Randy.Dunlap" <rddunlap@osdl.org>,
sean.hefty@intel.com, linux-kernel@vger.kernel.org,
woody@co.intel.com, bill.magro@intel.com, woody@jf.intel.com,
infiniband-general@lists.sourceforge.net
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in theLinux kernel
Date: Thu, 5 Feb 2004 19:57:55 -0600 [thread overview]
Message-ID: <20040206015754.GQ11222@kalmia.hozed.org> (raw)
In-Reply-To: <08628CA53C6CBA4ABAFB9E808A5214CB01DB96F2@mercury.infiniconsys.com>
On Thu, Feb 05, 2004 at 05:02:30PM -0500, Tillier, Fabian 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.
This is another issue... I think we should have a mechanism to allow
user code to call functions in user mode that are exported by the
kernel. Like the gettimeofday() syscall bypass stuff which I have heard
about but can't remember the details of.
The linux kernel obviously knows exactly what kind of processor it is
running on, and should be able to know exactly what the best memcpy()
function is. This should be exported to userspace instead of depending
on glibc to ask the kernel what cpu it has, and hope glibc has
reasonably optimized code.
The same interface would quite easily solve the infiniband atomic
locking issues.
Anyone in the infiniband industry please take note, we probably should
have had this discussion a year ago, and remember this next time.
next prev parent reply other threads:[~2004-02-06 1:57 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 22:02 Tillier, Fabian
2004-02-06 1:57 ` Troy Benjegerdes [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 17:55 Woodruff, Robert J
2004-02-24 18:03 ` Greg KH
[not found] <mailman.1076018705.12618.linux-kernel2news@redhat.com>
2004-02-09 1:51 ` Pete Zaitcev
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 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=20040206015754.GQ11222@kalmia.hozed.org \
--to=hozer@hozed.org \
--cc=bill.magro@intel.com \
--cc=cfriesen@nortelnetworks.com \
--cc=ftillier@infiniconsys.com \
--cc=greg@kroah.com \
--cc=infiniband-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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®