All of lore.kernel.org
 help / color / mirror / Atom feed
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] ***SPAM*** InfiniBand/RDMA merge plans for 2.6.27
Date: Mon, 14 Jul 2008 19:42:54 +0300	[thread overview]
Message-ID: <487B820E.4020002@mellanox.co.il> (raw)
In-Reply-To: <ada8ww5jbaf.fsf@cisco.com>

Roland Dreier wrote:
> Core:
>
>  - I'm waiting to merge the RDMA_CM_EVENT_ADDR_CHANGE changes that
>    depend on core networking changes until such changes are upstream.
>    Or, please remind me when that happens.
>
>  - Jack's XRC patch set.  I think we're getting closer to converging
>    here, and I hope to get this merged but we're getting down to the
>    wire, so we'll see.
>   
I hope we can get those in
> HW specific:
>
>  - Yevgeny's mlx4 changes.  We'll see how much time is left after I
>    get done with XRC (which is before this on my list) but to be
>    honest I'm not sure how mergeable a lot of this is without the
>    mlx4_en patches that actually use it.
>   
We just posted the mlx4_en patches, and we need to coordinate the merge 
of them together
>  - I've been working on memory management extensions support for mlx4,
>    but I'm not sure if it will be ready in time.  Firmware for this
>    may not be released for a while so it ain't urgent anyway.
>   
We are testing the patches and we already have FW that enable them.
I agree its not urgent but it would be good to have it, so ULPs that are 
interested can be tested over IB too.
> Here are a few topics that I believe will not be ready in time for the
> 2.6.27 window and will need to wait for 2.6.28 at least:
>
>  - Multiple CQ event vector support.  No one has convinced me that we
>    know how ULPs or userspace apps should decide which vector to use,
>    and hence little progress has been made since we deferred this
>    during the 2.6.23 merge window.
>   
We should progress this one even if we missed 2.6.27, especially we need 
it for RSS, and I know also RDS can gain from it.

Tziporet

  parent reply	other threads:[~2008-07-14 16:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  5:16 InfiniBand/RDMA merge plans for 2.6.27 Roland Dreier
2008-07-14 13:50 ` [ofa-general] ***SPAM*** " Eli Cohen
2008-07-15  6:52   ` Roland Dreier
2008-07-14 16:42 ` Tziporet Koren [this message]
2008-07-15 19:11   ` Roland Dreier
     [not found]     ` <15ddcffd0807151220m37204055rf6890037b445bd34@mail.gmail.com>
2008-07-15 19:36       ` Roland Dreier
2008-07-17  9:03         ` Tziporet Koren
2008-07-15  6:45 ` Jack Morgenstein
2008-07-15  6:52   ` Roland Dreier
2008-07-17  7:31 ` [ofa-general] " Or Gerlitz
2008-07-17  7:37   ` David Miller
2008-07-17  7:44     ` Or Gerlitz

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=487B820E.4020002@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 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.