linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Ira Snyder <iws@ovro.caltech.edu>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	shemminger@vyatta.com, David Miller <davem@davemloft.net>
Subject: Re: [PATCH RFC v5] net: add PCINet driver
Date: Mon, 12 Jan 2009 18:56:12 +0100	[thread overview]
Message-ID: <200901121856.12814.arnd@arndb.de> (raw)
In-Reply-To: <1231630355.2142.92.camel@pasglop>

On Sunday 11 January 2009, Benjamin Herrenschmidt wrote:
> On Thu, 2009-01-08 at 13:51 -0800, Ira Snyder wrote:
> > The guests (PowerPC computers running Linux) are PCI cards in the host
> > system (an Intel Pentium3-M system). The guest computers can access all
> > of the host's memory. The guests provide a 1MB (movable) window into
> > their memory.
> > 
> > The PowerPC computers also have a DMA controller, which I've used to get
> > better throughput from my driver. I have a way to create interrupts to
> > both the host and guest systems.
> 
> That looks -very- similar to the PCI driver for CAB and Cell triblades
> that was, I think, submitted a while ago. Arnd what's the status with
> that driver ?

Complicated ;-)

There were two device drivers for the Axon PCIe endpoint (from Mercury
and IBM), but both were abandoned due to being too complex to get into
a mergeable stage, and all the original developers are doing other work
now.

I'm maintaining the IBM driver now, but have no plans to submit that
for inclusion. I hope that I can soon find more time to work on a
replacement driver that will provide the right abstraction through
virtio for kernel drivers, plus a ibverbs user interface for direct
application programming. It should also have pluggable backends to
support not only Cell hardware but anything with a similar hardware
implementation.

I did make a presentation about this at the Plumbers Conference, see
http://userweb.kernel.org/%7Earnd/papers/plumbers08/plumbers-slides.pdf.
Since then, I have come to a much clearer idea of what needs to be
done, but not more actual code.

	Arnd <><

  reply	other threads:[~2009-01-12 17:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 19:50 [PATCH RFC v5] net: add PCINet driver Ira Snyder
2009-01-08 19:16 ` David Miller
2009-01-08 19:27   ` Ira Snyder
2009-01-08 21:51     ` Ira Snyder
2009-01-10 23:32       ` Benjamin Herrenschmidt
2009-01-12 17:56         ` Arnd Bergmann [this message]
2009-01-13  2:32       ` Rusty Russell
2009-01-13  3:34         ` Ira Snyder
2009-01-13 16:33           ` Arnd Bergmann
2009-01-13 16:40             ` Ira Snyder
2009-01-13 17:42               ` Arnd Bergmann
2009-01-15  0:12                 ` Ira Snyder
2009-01-15 12:58                   ` Arnd Bergmann
2009-01-15 16:54                     ` Ira Snyder
2009-01-15 17:53                       ` Arnd Bergmann
2009-01-15 18:20                         ` Ira Snyder
2009-01-15 20:57                           ` Arnd Bergmann
2009-01-15 23:27                             ` Ira Snyder
2009-01-15 19:21                         ` Ira Snyder
2009-01-15 21:22                           ` Arnd Bergmann
2009-01-15 21:40                             ` Ira Snyder
2009-01-15 22:53                               ` Arnd Bergmann
2009-01-15 23:31                                 ` Ira Snyder
2009-01-16  9:15                               ` Jan-Bernd Themann

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=200901121856.12814.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=iws@ovro.caltech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).