From: Christoph Lameter <cl@gentwo.org>
To: Greg KH <greg@kroah.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem
Date: Fri, 13 Jun 2014 11:56:08 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1406131155080.913@gentwo.org> (raw)
In-Reply-To: <20140611194504.GA2683@kroah.com>
On Wed, 11 Jun 2014, Greg KH wrote:
> > Often the kernel subsystems are impeding performance. In high speed
> > computing we regularly bypass the kernel network subsystems, block I/O
> > etc. Direct hardware access means though that one is explosed to the ugly
> > particularities of how a certain device has to be handled. Can we have the
> > cake and eat it too by defining APIs that allow low level hardware access
> > but also provide hardware abstraction (maybe limited to certain types of
> > devices).
>
> What type of devices are you wanting here, block and networking or
> something else? We have the uio interface if you want to (and know how
> to) talk to your hardware directly from userspace, what else do you want
> to do here that this doesn't provide?
Block and networking mainly. The userspace VFIO API exposes device
specific registers. We need something that is a decent abstraction.
IBverbs is something like that but it could be done much better.
next prev parent reply other threads:[~2014-06-13 16:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 19:03 Christoph Lameter
2014-06-11 19:26 ` Daniel Phillips
2014-06-11 19:45 ` Greg KH
2014-06-12 13:35 ` John W. Linville
2014-06-13 16:57 ` Christoph Lameter
2014-06-13 17:31 ` Greg KH
2014-06-13 17:59 ` Christoph Lameter
2014-06-13 19:18 ` Stephen Hemminger
2014-06-13 22:30 ` Christoph Lameter
2014-06-13 16:56 ` Christoph Lameter [this message]
2014-06-13 17:30 ` Greg KH
2014-06-13 17:55 ` James Bottomley
2014-06-13 18:41 ` Christoph Lameter
2014-06-16 11:39 ` Thomas Petazzoni
2014-06-16 14:05 ` Christoph Lameter
2014-06-16 14:09 ` Thomas Petazzoni
2014-06-16 14:28 ` Christoph Lameter
2014-06-13 18:01 ` Christoph Lameter
2014-06-13 18:25 ` Greg KH
2014-06-13 18:54 ` Christoph Lameter
2014-06-11 20:08 ` josh
2014-06-11 20:15 ` Andy Lutomirski
2014-06-11 20:52 ` Dave Hansen
2014-06-12 6:59 ` Phillip Lougher
2014-06-13 17:02 ` Christoph Lameter
2014-06-13 21:36 ` Benjamin Herrenschmidt
2014-06-13 22:23 ` Rik van Riel
2014-06-13 23:04 ` Christoph Lameter
2014-06-14 1:19 ` Phillip Lougher
2014-06-16 14:04 ` Christoph Lameter
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=alpine.DEB.2.10.1406131155080.913@gentwo.org \
--to=cl@gentwo.org \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.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