From: Sean Hefty <mshefty@ichips.intel.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Pradeep Satyanarayana <pradeeps@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Re: [ofa-general] Updated InfiniBand/RDMA merge plans for 2.6.24
Date: Tue, 09 Oct 2007 10:18:37 -0700 [thread overview]
Message-ID: <470BB7ED.7070007@ichips.intel.com> (raw)
In-Reply-To: <ada7ilwjp2l.fsf@cisco.com>
> Can you give a link to your current final version of the patch?
>
> Sean, what's your opinion of where we stand?
Let me look back over the last version that was sent and reply back
later today or tomorrow. Several of my initial comments were on code
structure.
> Since module parameters create a userspace-visible interface that we
> are stuck with for a long time, we definitely have to get at least
> that much right before merging.
I was taking a slightly different view of the design. It would be nice
to agree on whether SRQ should be separated from the QP type before
merging upstream, even if the implementation doesn't immediately support
all available options.
- Sean
next prev parent reply other threads:[~2007-10-09 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 23:18 Updated InfiniBand/RDMA merge plans for 2.6.24 Roland Dreier
2007-10-07 2:02 ` [ofa-general] " Pradeep Satyanarayana
2007-10-09 15:16 ` Roland Dreier
2007-10-09 17:18 ` Sean Hefty [this message]
2007-10-09 18:49 ` Pradeep Satyanarayana
2007-10-07 16:19 ` Steve Wise
2007-10-08 23:54 ` Roland Dreier
2007-10-09 14:15 ` Steve Wise
2007-10-08 6:38 ` Jack Morgenstein
2007-10-08 14:48 ` Roland Dreier
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=470BB7ED.7070007@ichips.intel.com \
--to=mshefty@ichips.intel.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pradeeps@linux.vnet.ibm.com \
--cc=rdreier@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.