[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTin69m0kK6bqUiwYeHRQT0Ehso16xA6RBtBFFgW3@mail.gmail.com>
Date: Tue, 14 Sep 2010 15:28:00 -0700
From: Andrew Grover <andy.grover@...il.com>
To: Zach Brown <zach.brown@...cle.com>
Cc: Or Gerlitz <ogerlitz@...taire.com>,
Andy Grover <andy.grover@...cle.com>,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
RDS Devel <rds-devel@....oracle.com>,
Roland Dreier <rdreier@...co.com>
Subject: Re: [rds-devel] net-next pull request: RDS
On Tue, Sep 14, 2010 at 11:35 AM, Zach Brown <zach.brown@...cle.com> wrote:
>> Zach Brown's "RDS/IB: print IB event strings as well as their number" - commit
>> 1bde04a63d532c2540d6fdee0a661530a62b1686 in net-next-2.6 looks perfect to
>> reside as a helper function in the core IB stack which can be in use by other
>> rdma drivers (e.g ipoib, iser, srp, etc).
>
> Yeah, if those other drivers were interested in the little helpers then it
> would make sense to bring the functionality up into the core stack.
>
> Note that there's another later commit in net-next that gives other event
> strings the same treatment: 59f740a6aeb2cde2f79fe0df38262d4c1ef35cd8 .
Since rds goes upstream via netdev not linux-rdma, it's a little
tricky.. any core ib helpers we added would not be in net-next so rds
wouldn't build. :) Once net-next gets pushed to mainline and Roland
pulls from that, then we'll be in a good position to put these helpers
where they should go, and change other ULPs to use them.
-- Andy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists