public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ira Snyder <iws@ovro.caltech.edu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, shemminger@vyatta.com,
	David Miller <davem@davemloft.net>,
	Jan-Bernd Themann <themann@de.ibm.com>
Subject: Re: [PATCH RFC v5] net: add PCINet driver
Date: Thu, 15 Jan 2009 13:40:56 -0800	[thread overview]
Message-ID: <20090115214056.GC9091@ovro.caltech.edu> (raw)
In-Reply-To: <200901152222.55006.arnd@arndb.de>

On Thu, Jan 15, 2009 at 10:22:53PM +0100, Arnd Bergmann wrote:
> On Thursday 15 January 2009, Ira Snyder wrote:
> > I have another question for you Arnd.
> > 
> > What did you use as the host and guest drivers when you ran virtio over
> > PCI? Did you use two unmodified instances of virtio_net (one on host,
> > one on guest) for networking, or did you write new virtio drivers for
> > those? How about for virtio_console (if you ran it at all).
> 
> Jan-Bernd may be able to tell you details about this, and send you the
> driver code that his interns implemented for it.
> This was only doing virtio_net between two machines using MMIO transfers,
> i.e. the DMA engine was unused, but there was a mailbox interrupt (if you
> have one of these, you won't need MSI, btw -- just write a DMA to it).
> 

Thanks. Jan-Bernd, I'm looking forward to any input you have.

I'd be happy enough to use mmio at this point. My early attempts with
this driver only used mmio as well. The DMA was bolted on later.

I do have mailboxes (two inbound, two outbound) which can generate
interrupts, as well as doorbell registers (one inbound, one outbound).
The doorbell register's bits are "write 1 to clear", and can only be
cleared by the opposite side.

All of them can cause interrupts over PCI. I used the doorbell registers
to communicate which action needed to be taken in my driver. One
doorbell for "receive packet(s)", another for "packet transmission(s)
complete", etc. I used the mailboxes to transfer characters for the
virtual serial port.

Ira

  reply	other threads:[~2009-01-15 21:41 UTC|newest]

Thread overview: 23+ 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
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 [this message]
2009-01-15 22:53                               ` Arnd Bergmann
2009-01-15 23:31                                 ` Ira Snyder

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=20090115214056.GC9091@ovro.caltech.edu \
    --to=iws@ovro.caltech.edu \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --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 \
    --cc=themann@de.ibm.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