On Wed, 2006-06-28 at 14:29 +1000, Herbert Xu wrote:
> On Wed, Jun 28, 2006 at 12:18:25AM -0400, Jeff Garzik wrote:
> >
> > A PCI device that presents itself as a SCSI controller, but under the
> > hood is really iSCSI-over-TCP smells like TOE. Running a virtualized
> > Linux guest on top of a
On Wed, 2006-06-28 at 00:18 -0400, Jeff Garzik wrote:
> Herbert Xu wrote:
> > On Tue, Jun 27, 2006 at 11:24:25PM -0400, Jeff Garzik wrote:
> >> I don't see how that position has changed?
> >>
> >> http://linux-net.osdl.org/index.php/TOE
> >
> > Well I must say that RDMA over TCP smells very much l
Herbert Xu wrote:
On Wed, Jun 28, 2006 at 12:18:25AM -0400, Jeff Garzik wrote:
A PCI device that presents itself as a SCSI controller, but under the
hood is really iSCSI-over-TCP smells like TOE. Running a virtualized
Linux guest on top of a proprietary stack [which provides networking
servic
On Wed, Jun 28, 2006 at 12:18:25AM -0400, Jeff Garzik wrote:
>
> A PCI device that presents itself as a SCSI controller, but under the
> hood is really iSCSI-over-TCP smells like TOE. Running a virtualized
> Linux guest on top of a proprietary stack [which provides networking
> services to gue
Herbert Xu wrote:
On Tue, Jun 27, 2006 at 11:24:25PM -0400, Jeff Garzik wrote:
I don't see how that position has changed?
http://linux-net.osdl.org/index.php/TOE
Well I must say that RDMA over TCP smells very much like TOE. They've
got an ARP table, a routing table, and presumably a TCP stac
On Tue, Jun 27, 2006 at 11:24:25PM -0400, Jeff Garzik wrote:
>
> I don't see how that position has changed?
>
> http://linux-net.osdl.org/index.php/TOE
Well I must say that RDMA over TCP smells very much like TOE. They've
got an ARP table, a routing table, and presumably a TCP stack.
Cheers,
--
Herbert Xu wrote:
On Wed, Jun 28, 2006 at 12:54:10PM +1000, Herbert Xu wrote:
Please give more specific reasons for needing these events because it
is certainly far from obvious from reading those documents.
Never mind, I've found your earlier messages on the list which explains
your reasons m
On Wed, Jun 28, 2006 at 12:54:10PM +1000, Herbert Xu wrote:
>
> Please give more specific reasons for needing these events because it
> is certainly far from obvious from reading those documents.
Never mind, I've found your earlier messages on the list which explains
your reasons more clearly. I
Steve Wise <[EMAIL PROTECTED]> wrote:
>
> The reason these devices need update events is because they typically
> cache this information in hardware and need to be notified when this
> information has been updated. For information on RDMA protocols, see:
> http://www.ietf.org/html.charters/rddp-c
Round 3 Changes:
- changed netlink msg for neighbour change to (RTM_NEIGHUPD)
- added netlink msg for PMTU change events (RTM_ROUTEUPD)
- added netlink messages for redirect (RTM_DELROUTE + RTM_NEWROUTE)
- tested neighbour change events via netlink for ipv4 and ipv6.
- tested redirect change even
10 matches
Mail list logo
