From: Jack Morgenstein <jackm@dev.mellanox.co.il>
To: general@lists.openfabrics.org
Cc: Roland Dreier <rdreier@cisco.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
tziporet@mellanox.co.il
Subject: Re: [ofa-general] InfiniBand/RDMA merge plans for 2.6.24
Date: Tue, 18 Sep 2007 09:09:49 +0200 [thread overview]
Message-ID: <200709180909.50029.jackm@dev.mellanox.co.il> (raw)
In-Reply-To: <adahclymos8.fsf@cisco.com>
On Thursday 13 September 2007 20:57, Roland Dreier wrote:
> HW specific:
>
> - I already merged patches to enable MSI-X by default for mthca and
> mlx4. I hope there aren't too many systems that get hosed if a
> MSI-X interrupt is generated.
>
> - Jack and Michael's mlx4 FMR support. Will merge I guess, although
> I do hope to have time to address the DMA API abuse that is being
> copied from mthca, so that mlx4 and mthca work in Xen domU.
>
> - ehca patch queue. Will merge, pending fixes for the few minor
> issues I commented on.
>
> - Steve's mthca router mode support. Would be nice to see a review
> from someone at Mellanox.
>
> - Arthur's mthca doorbell alignment fixes. I will experiment with a
> few different approaches and post what I like (and fix mlx4 as
> well). I hope Arthur can review.
>
> - Michael's mlx4 WQE shrinking patch. Not sure yet; I'll reply to
> the latest patch directly.
>
Missing from this list (IMPORTANT patch!):
[ofa-general] [PATCH 2 of 2] IB/mlx4: Handle new FW requirement for send request prefetching, for WQE sg lists
(Posted by me to list on Sept 4)
{patch header:
This is an addendum to Roland's commit 0e6e74162164d908edf7889ac66dca09e7505745
(June 18). This addendum adds prefetch headroom marking processing for s/g segments.
We write s/g segments in reverse order into the WQE, in order to guarantee
that the first dword of all cachelines containing s/g segments is written last
(overwriting the headroom invalidation pattern). The entire cacheline will thus
contain valid data when the invalidation pattern is overwritten.
}
This patch series (1 of 2 is for libmlx4, the same issue).
============================================================
Also, I'm now posting (in a separate post) the following patch to mlx4, which is important:
display the following device information via sysfs:
board_id, fw_ver, hw_rev, hca_type.
The info is displayed under directory /sys/class/infiniband/mlx4_x, where x is
the pci bus sequence number (starting from zero).
This patch makes information available to ibstat and ibv_devinfo under the
same directory as is used for tavor/arbel/sinai -- thus requiring no userspace
modifications.
- Jack
next prev parent reply other threads:[~2007-09-18 7:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 17:57 Roland Dreier
2007-09-13 18:04 ` [ofa-general] " Steve Wise
2007-09-13 18:56 ` Jeff Garzik
2007-09-13 18:59 ` Steve Wise
2007-09-13 19:55 ` Jeff Garzik
2007-09-14 12:55 ` Evgeniy Polyakov
2007-09-13 21:12 ` Roland Dreier
2007-09-13 21:11 ` Roland Dreier
2007-09-13 22:59 ` Michael Chan
2007-09-14 16:18 ` Roland Dreier
2007-09-14 21:09 ` Michael Chan
2007-09-15 14:03 ` Steve Wise
2007-09-13 18:20 ` Sean Hefty
2007-09-13 21:02 ` Roland Dreier
2007-09-14 17:45 ` Sean Hefty
2007-10-02 18:26 ` Roland Dreier
2007-10-02 18:50 ` Sean Hefty
2007-10-05 23:10 ` Roland Dreier
[not found] ` <1190034015.6272.83.camel@hrosenstock-ws.xsigo.com>
2007-09-18 9:48 ` Tziporet Koren
2007-09-13 18:22 ` Shirley Ma
2007-09-13 21:00 ` Roland Dreier
2007-09-16 8:50 ` [ofa-general] " Or Gerlitz
2007-09-17 22:11 ` Roland Dreier
2007-09-18 7:09 ` Jack Morgenstein [this message]
2007-09-18 16:34 ` Michael S. Tsirkin
2007-09-18 17:18 ` Roland Dreier
2007-09-18 17:22 ` Michael S. Tsirkin
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=200709180909.50029.jackm@dev.mellanox.co.il \
--to=jackm@dev.mellanox.co.il \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=tziporet@mellanox.co.il \
/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
Powered by JetHome