From: Tziporet Koren <tziporet@dev.mellanox.co.il>
To: Roland Dreier <rdreier@cisco.com>
Cc: general@lists.openfabrics.org, linux-kernel@vger.kernel.org
Subject: Re: [ofa-general] InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what's in infiniband.git)
Date: Wed, 02 Apr 2008 15:31:32 +0300 [thread overview]
Message-ID: <47F37CA4.8000109@mellanox.co.il> (raw)
In-Reply-To: <adave31bayd.fsf@cisco.com>
Roland Dreier wrote:
> Core:
>
> - I did a bunch of cleanups all over drivers/infiniband and the
> gcc and sparse warning noise is down to a pretty reasonable level.
> Further cleanups welcome of course.
>
We want to add send with invalidate & mask compare and swap.
Eli will be able to send the patches next week and since they are small
I think they can be in for 2.6.26
> ULPs:
>
> - I merged Eli's IPoIB stateless offload changes for checksum
> offload and LSO changes. The interrupt moderation changes are
> next, and should not be a problem to merge. Please test IPoIB
> on all sorts of hardware!
>
What about the split CQ for UD mode? It's improved the IPoIB performance
for small messages significantly.
>
> HW specific:
>
>
mlx4- we plan to send patches for the low level driver only to enable
mlx4_en. These only affect our low level driver.
Should be ready next week. I hope these can get in too.
> Here are a few topics that I believe will not be ready in time for the
> 2.6.26 window and will need to wait for 2.6.27 at least:
>
> - XRC. I still don't have a good feeling that we have settled on all
> the nuances of the ABI we want to expose to userspace for this, and
> ideally I would like to understand how ehca LL QPs fit into the
> picture as well.
>
I think we should try to push for XEC in 2.6.26 since there are already
MPI implementation that use it and this ties them to use OFED only.
Also this feature is stable and now being defined in IBTA
Not taking it causing changes between OFED and the kernel and your
libibverbs and we wish to avoid such gaps.
Is there any thing we can do to help and make it into 2.6.26?
next prev parent reply other threads:[~2008-04-02 12:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 20:02 Roland Dreier
2008-04-01 16:55 ` [ofa-general] " Shirley Ma
2008-04-02 7:22 ` Shirley Ma
2008-04-02 15:27 ` Roland Dreier
2008-04-02 17:11 ` Richard Frank
2008-04-02 16:15 ` Roland Dreier
2008-04-02 17:18 ` Richard Frank
2008-04-02 16:26 ` Roland Dreier
2008-04-02 17:28 ` Richard Frank
2008-04-02 17:24 ` Richard Frank
2008-04-02 16:29 ` [ofa-general] InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what'sin infiniband.git) Scott Weitzenkamp (sweitzen)
2008-04-02 17:37 ` Richard Frank
2008-04-02 16:46 ` Scott Weitzenkamp (sweitzen)
2008-04-02 18:00 ` Richard Frank
2008-04-02 17:04 ` Scott Weitzenkamp (sweitzen)
2008-04-02 12:31 ` Tziporet Koren [this message]
2008-04-02 16:19 ` [ofa-general] InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what's in infiniband.git) Roland Dreier
2008-04-03 11:40 ` Tziporet Koren
2008-04-04 20:26 ` Richard Frank
2008-04-04 19:34 ` Roland Dreier
2008-04-04 22:21 ` Richard Frank
2008-04-04 5:54 ` Or Gerlitz
[not found] <OF1D776305.7E25BAA6-ON8725741F.005B027C-8825741F.002F5161@us.ibm.com>
2008-04-02 16:37 ` 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=47F37CA4.8000109@mellanox.co.il \
--to=tziporet@dev.mellanox.co.il \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®