From: David Miller <davem@davemloft.net>
To: andy.grover@oracle.com
Cc: netdev@vger.kernel.org, rds-devel@oss.oracle.com
Subject: Re: [PATCH net-next 0/5] RDS: TCP transport support
Date: Sun, 23 Aug 2009 19:13:42 -0700 (PDT) [thread overview]
Message-ID: <20090823.191342.86319826.davem@davemloft.net> (raw)
In-Reply-To: <1250893715-21939-1-git-send-email-andy.grover@oracle.com>
From: Andy Grover <andy.grover@oracle.com>
Date: Fri, 21 Aug 2009 15:28:30 -0700
> This patch series adds a TCP transport for RDS. Instead of requiring
> an IB queue pair for communication between two nodes, it may instead
> tunnel traffic over a TCP connection. This makes RDS usable by
> people without IB hardware, or in a VM.
>
> In addition, this patchset modularizes RDS into an rds core module,
> an rds_rdma module (for Infiniband and iWARP) and rds_tcp module. RDS
> itself no longer has a dependency on IB (the rds_rdma module does).
>
> This code has been tested and verified to work and perform acceptably,
> but has not yet had intensive performance analysis.
All applied to net-next-2.6, thanks.
I'll push it out to kernel.org after some build tests.
prev parent reply other threads:[~2009-08-24 2:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 22:28 [PATCH net-next 0/5] RDS: TCP transport support Andy Grover
2009-08-21 22:28 ` [PATCH 1/5] RDS: Add TCP transport to RDS Andy Grover
2009-08-21 22:28 ` [PATCH 2/5] RDS: Export symbols from core RDS Andy Grover
2009-08-21 22:28 ` [PATCH 3/5] RDS: Modularize RDMA and TCP transports Andy Grover
2009-08-21 22:28 ` [PATCH 4/5] RDS: Track transports via an array, not a list Andy Grover
2009-08-21 22:28 ` [PATCH 5/5] RDS: Add a debug message suggesting to load transport modules Andy Grover
2009-08-24 2:13 ` David Miller [this message]
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=20090823.191342.86319826.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy.grover@oracle.com \
--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