netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@voltaire.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: general@lists.openfabrics.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Jay Vosburgh <fubar@us.ibm.com>,
	"Michael S. Tsirkin" <mst@mellanox.co.il>
Subject: Re: [ofa-general] InfiniBand/RDMA merge plans for 2.6.24
Date: Sun, 16 Sep 2007 11:50:07 +0300	[thread overview]
Message-ID: <46ECEE3F.60301@voltaire.com> (raw)
In-Reply-To: <adahclymos8.fsf@cisco.com>

Roland Dreier wrote:
> With 2.6.24 probably opening in the not-too-distant future, it's
> probably a good time to review what my plans are for when the merge
> window opens.

> Core:
>  - Sean's QoS changes.  These look fine at first glance, and I just
>    plan to understand the backwards compatibility story (ie how this
>    works with an old SM) and merge.  Anyone who objects let me know.

Hi Roland,

I have reviewed the qos patches and provided comments which were 
deployed in v2 of the series. I also tested it (ipoib and iser which is 
rdma-cm based) against the Voltaire SM/SA to see that nothing was 
broken. I will send you a "reviewed by:" signature.

> ULPs:

> [ofa-general] [PATCH RFC] IB/ipoib: enable IGMP for userpsace multicast IB apps
The IGMP enabling patch posted by me on September 2nd isn't on your list
http://lists.openfabrics.org/pipermail/general/2007-September/040250.html
can you add it?


>  - Moni's IPoIB bonding support.  This seems mostly an issue of
>    getting the core bonding maintainer's attention.  However getting a
>    Reviewed-by: for the IPoIB changes wouldn't hurt too.

Jay Vosburgh, the bonding driver maintainer just sent an ack on all 
patch series. As for the IPoIB changes, there are three patches, where 
two of them, namely
> [PATCH 02/11] IB/ipoib: Notify the world before doing unregister
> [PATCH 04/11] IB/ipoib: Verify address handle validity on send
are handling a corner-case problems pointed by Michael Tsirkin.
Michael, will you be able to look on it and provide a reviewed-by 
signature? the third patch
> [PATCH 03/11] IB/ipoib: Bound the net device to the ipoib_neigh structue
is somehow much more simple, I don't think more review is needed for it.

>  - Eli and Michael's IPoIB stateless offload (checksum offload, LSO,
>    LRO, etc).  It's a big series that makes quite a few core changes.
>    I think it needs some careful review and is probably at risk of
>    missing this merge window.  Sorting in order of invasiveness so we
>    can merge at least some of it (if splitting it makes sense) might
>    be a good idea.

Just for the record, the 'etc' above relates to the interrupt moderation 
support (mlx4, core, ipoib {config through ethertool, usage). Among 
other things, what is not clear to me here is if/how this goes 
hand-in-hand with NAPI.

As you saw the patch adding checksum offload support had a long thread, 
and I think the discussion has reached the point where Michael is 
waiting for your take on it.

As for the LSO, LRO patches, I did not see any review comment.

I will see that I can review from the series, to begin with, will send 
Eli some comments and questions.

> HW specific:
>  - 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.

This patch series is somehow important as without them iser is useless 
over connectx. Can be nice if you merge this and at max fix the abuse later.

Or.


  parent reply	other threads:[~2007-09-16  9:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 17:57 InfiniBand/RDMA merge plans for 2.6.24 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
2007-09-17 13:00   ` Hal Rosenstock
2007-09-18  9:48     ` Tziporet Koren
2007-09-13 18:22 ` Shirley Ma
2007-09-13 21:00   ` Roland Dreier
2007-09-13 22:16     ` [ofa-general] " Shirley Ma
2007-09-14 16:09       ` Roland Dreier
2007-09-14 18:36         ` Shirley Ma
2007-09-17 21:47           ` [ofa-general] " Roland Dreier
2007-09-17 22:24             ` Shirley Ma
2007-10-03 18:43             ` Shirley Ma
2007-09-16  8:50 ` Or Gerlitz [this message]
2007-09-17 22:11   ` [ofa-general] " Roland Dreier
2007-09-18  7:09 ` Jack Morgenstein
2007-09-19  6:19   ` [ofa-general] " Michael S. Tsirkin
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=46ECEE3F.60301@voltaire.com \
    --to=ogerlitz@voltaire.com \
    --cc=fubar@us.ibm.com \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).