public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Alekseys Senin <alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: Eli Cohen <eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
	Moni Shoua <monis-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
	"ewg@openfabrics.org"
	<ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [ewg] [PATCH v4] IB Core: RAW ETH support
Date: Tue, 15 Jun 2010 14:14:36 -0700	[thread overview]
Message-ID: <aday6eguhfn.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <1276513450.30132.51.camel-uOVkuFIEnOODI2cvxHXf6UEOCMrvLtNR@public.gmane.org> (Alekseys Senin's message of "Mon, 14 Jun 2010 14:04:10 +0300")

 > I tested it before on the Roland tree ( iboe branch ) and it fails,
 > because it writen in the way suitable for OFED. If adapt the patch to
 > the Roland tree, then appling Mellanox OFED patches will fail, because
 > it changes the same functions in the code.
 > Here is one example:
 > Look at __mlx4_ib_modify_qp at the Roland tree - there is no RAW_ETY
 > support. But in the OFED version of the same function this support is
 > present.
 > RAW_ETH patch modify this function and looking for RAW_ETY word and
 > without this RAW_ETH Mellanox patch will fail.

Don't take this too personally -- I picked a semi-random email in this
thread to reply to; this is pretty broadly targeted.

<rant>

What the hell is the thinking behind introducing IB_QPT_RAW_ETH?  You're
inserting an enum value before IB_QPT_RAW_ETY, so any old userspace
passing in IB_QPT_RAW_ETY will silently get different behavior depending
on the kernel version.  And you're creating two constands that differ in
a single letter (IB_QPT_RAW_ETY vs. IB_QPT_RAW_ETH).  How are you going
to explain that to users?  How is anyone ever going to get it right?
For that matter, what exactly does IB_QPT_RAW_ETH mean?

This all seems to be a symptom of how broken our development process
is.  Yes, unfortunately I can't spend as much time reviewing and
applying patches as I might like, and I apologize for that.  But if we
have all the RDMA developers piling up shit in their little area and
then sending it on to be merged as soon as it kind of works, without
thinking about design or maintainability and without ever doing any
review, then I'm always going to have an expanding review backlog.

And then we have OFED compounding problems -- "Oh that's a nice pile of
shit you've built there.  We better ship it to users while it's still
steaming."  How about if OFED developers take a little time to think
things through?

</rant>

In other words, can someone explain the plan for this raw QP stuff to me?

 - R.
-- 
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org> || For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2010-06-15 21:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E113D394D7C5DB4F8FF691FA7EE9DB4439A76E8632@MTLMAIL.mtl.com>
     [not found] ` <1276513450.30132.51.camel@alst60.voltaire.com>
     [not found]   ` <1276513450.30132.51.camel-uOVkuFIEnOODI2cvxHXf6UEOCMrvLtNR@public.gmane.org>
2010-06-15 21:14     ` Roland Dreier [this message]
     [not found]       ` <aday6eguhfn.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-06-16 14:09         ` [ewg] [PATCH v4] IB Core: RAW ETH support Steve Wise
     [not found]           ` <4C18DB37.6050501-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-06-16 15:47             ` Moni Shoua
     [not found]               ` <4C18F21D.3050502-hKgKHo2Ms0F+cjeuK/JdrQ@public.gmane.org>
2010-06-16 15:54                 ` Steve Wise
     [not found]                   ` <4C18F39D.3040609-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-06-16 15:59                     ` Tung, Chien Tin
2010-06-16 17:02             ` Jason Gunthorpe
     [not found]               ` <20100616170234.GA2932-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-06-16 17:12                 ` Steve Wise
     [not found]                   ` <4C1905E6.2000304-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-06-16 17:52                     ` Jason Gunthorpe
     [not found]                       ` <20100616175259.GF4630-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-06-16 18:35                         ` Steve Wise
     [not found]                           ` <4C19195B.1080003-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-06-17 13:58                             ` Doug Ledford
2010-06-17 14:10                     ` Doug Ledford
2010-06-16 14:53         ` [ewg] " Moni Shoua
     [not found]           ` <4C18E557.5050804-hKgKHo2Ms0F+cjeuK/JdrQ@public.gmane.org>
2010-06-23 17:31             ` Roland Dreier
     [not found]               ` <ada4ogtvenr.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-06-24 19:44                 ` Moni Shoua

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=aday6eguhfn.fsf@roland-alpha.cisco.com \
    --to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
    --cc=alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    --cc=eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
    --cc=ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=monis-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    /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