From: Roland Dreier <rdreier@cisco.com>
To: David Miller <davem@davemloft.net>
Cc: rds-devel@oss.oracle.com, general@lists.openfabrics.org,
netdev@vger.kernel.org
Subject: Re: [ofa-general] Re: [PATCH 0/26] Reliable Datagram Sockets (RDS), take 2
Date: Wed, 25 Feb 2009 10:16:18 -0800 [thread overview]
Message-ID: <adaeixmtma5.fsf@cisco.com> (raw)
In-Reply-To: <20090225.000628.108688119.davem@davemloft.net> (David Miller's message of "Wed, 25 Feb 2009 00:06:28 -0800 (PST)")
> It's making real sockets, using the real networking stack,
> using up real IP port/address pairs recognized by the rest
> of the real networking stack, and doing RDMA over that
> connection.
>
> That's not allowed.
>
> We always said that if these RDMA things are in the tree,
> they should use their own IP addresses and that are not
> visible to the real Linux networking stack.
How is what the RDS code is doing any different than what the (upstream)
NFS/RDMA and iSER code does? It uses the same rdma_xxx() interfaces for
handling connections.
- R.
next prev parent reply other threads:[~2009-02-25 18:16 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 1:30 [ofa-general] [PATCH 0/26] Reliable Datagram Sockets (RDS), take 2 Andy Grover
2009-02-25 1:30 ` [ofa-general] [PATCH 01/26] RDS: Socket interface Andy Grover
2009-02-25 1:30 ` [PATCH 02/26] RDS: Main header file Andy Grover
2009-02-25 1:30 ` [PATCH 03/26] RDS: Congestion-handling code Andy Grover
2009-02-25 1:30 ` [PATCH 04/26] RDS: Transport code Andy Grover
2009-02-25 1:30 ` [PATCH 05/26] RDS: Info and stats Andy Grover
2009-02-25 1:30 ` [PATCH 06/26] RDS: Connection handling Andy Grover
2009-02-25 1:30 ` [PATCH 07/26] RDS: loopback Andy Grover
2009-02-25 1:30 ` [PATCH 08/26] RDS: sysctls Andy Grover
2009-02-25 1:30 ` [PATCH 09/26] RDS: Message parsing Andy Grover
2009-02-25 1:30 ` [PATCH 10/26] RDS: send.c Andy Grover
2009-02-25 1:30 ` [PATCH 11/26] RDS: recv.c Andy Grover
2009-02-25 1:30 ` [PATCH 12/26] RDS: RDMA support Andy Grover
2009-02-25 1:30 ` [PATCH 13/26] RDS/IB: Infiniband transport Andy Grover
2009-02-25 1:30 ` [PATCH 14/26] RDS/IB: Ring-handling code Andy Grover
2009-02-25 1:30 ` [PATCH 15/26] RDS/IB: Implement RDMA ops using FMRs Andy Grover
2009-02-25 1:30 ` [PATCH 16/26] RDS/IB: Implement IB-specific datagram send Andy Grover
2009-02-25 1:30 ` [PATCH 17/26] RDS/IB: Receive datagrams via IB Andy Grover
2009-02-25 1:30 ` [PATCH 18/26] RDS/IB: Stats and sysctls Andy Grover
2009-02-25 1:30 ` [PATCH 19/26] RDS: Add iWARP support Andy Grover
2009-02-25 1:30 ` [PATCH 20/26] RDS: Common RDMA transport code Andy Grover
2009-02-25 1:30 ` [PATCH 21/26] RDS: Documentation Andy Grover
2009-02-25 1:30 ` [PATCH 22/26] RDS: Kconfig and Makefile Andy Grover
2009-02-25 1:30 ` [PATCH 23/26] RDS: Add AF and PF #defines for RDS sockets Andy Grover
2009-02-25 7:26 ` [ofa-general] " David Miller
2009-02-25 11:36 ` Rémi Denis-Courmont
2009-02-25 11:58 ` David Miller
2009-02-25 18:45 ` Andrew Grover
2009-02-25 1:30 ` [PATCH 24/26] RDS: Add MAINTAINERS entry Andy Grover
2009-02-25 1:30 ` [PATCH 25/26] RDS: Add userspace header Andy Grover
2009-02-25 1:30 ` [PATCH 26/26] RDS: Add RDS to AF key strings Andy Grover
2009-02-25 7:28 ` [PATCH 0/26] Reliable Datagram Sockets (RDS), take 2 David Miller
2009-02-25 8:04 ` [ofa-general] " Or Gerlitz
2009-02-25 8:06 ` David Miller
2009-02-25 9:46 ` Or Gerlitz
2009-02-25 18:16 ` Roland Dreier [this message]
2009-02-25 18:43 ` Andrew Grover
2009-02-25 21:45 ` [ofa-general] " David Miller
2009-02-27 8:01 ` David Miller
2009-02-27 18:21 ` Andrew Grover
2009-02-27 17:08 ` [ofa-general] " Andi Kleen
2009-02-28 1:53 ` ***SPAM*** " Andrew Grover
2009-02-28 5:56 ` Andi Kleen
2009-02-28 20:44 ` ***SPAM*** " Andrew Grover
2009-02-28 22:36 ` Andi Kleen
2009-03-01 0:58 ` ***SPAM*** " Andrew Grover
2009-03-01 1:50 ` Andi Kleen
2009-03-03 22:19 ` ***SPAM*** " Andrew Grover
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=adaeixmtma5.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=davem@davemloft.net \
--cc=general@lists.openfabrics.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.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).