All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Bart Van Assche <bart.vanassche@sandisk.com>,
	Doug Ledford <dledford@redhat.com>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	target-devel <target-devel@vger.kernel.org>
Subject: Re: [PATCH 0/4] IB/srpt and the percpu_ida conversion
Date: Fri, 8 Apr 2016 01:01:10 +0200	[thread overview]
Message-ID: <20160407230110.GA9842@lst.de> (raw)
In-Reply-To: <1460068181.18732.23.camel@haakon3.risingtidesystems.com>

On Thu, Apr 07, 2016 at 03:29:41PM -0700, Nicholas A. Bellinger wrote:
> I asked to not revert the percpu_ida conversion and again you simply
> ignored subsystem maintainer feedback, and included a different
> percpu_ida conversion without using alloc_session callback that still
> does pre-allocation of buffers before session login even completes.

He doesn't revert it after the patch series, but reverts it first
to then do it properly.  If you don't like that it's fine to ask
Bart to resend with a different patch ordering, but it would be really
helpful to do it politely.

> The whole point of the alloc_session callback is so that extra
> pre-allocation doesn't happen until after se_node_acl lookup has
> finished, and is what ib_srpt needs to be using given SRP's completely
> existent spec level security model.

Your original patch didn't use the alloc_session callback either,
so I don't really see the fuzz here.  I don't see how it makes things
clearer, but if you ask politely, and provide a detailed and valid
explanation I'm pretty sure Bart will adopt the series to your taste.

> 
> In any event, I'm fixing the regression ahead of the next v4.6-rc PULL
> in:
> 
> http://www.spinics.net/lists/target-devel/msg12535.html
> 
> Any issues you find with this patch should be sent out as an incremental
> patch, and not rolling your own concoction.

That patch doesn't work.  While it's great to have a maintainer that
sets overall architectural direction it also really helps to work nicely
with contributors that have detailed experience with the transport (or in
this case even wrote the original driver).

I think a lot of these disagreements could be sorted out much better if
you work with Bart at a technical level rather than having a personal
vandetta.

  parent reply	other threads:[~2016-04-07 23:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 18:56 [PATCH 0/4] IB/srpt and the percpu_ida conversion Bart Van Assche
2016-04-06 18:56 ` [PATCH 1/4] IB/srpt: Revert "Convert to percpu_ida tag allocation" Bart Van Assche
2016-04-06 18:57 ` [PATCH 2/4] IB/srpt: Report login failures only once Bart Van Assche
     [not found]   ` <57055BFF.9060607-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-04-07 13:40     ` Christoph Hellwig
2016-04-06 18:57 ` [PATCH 3/4] IB/srpt: Introduce two helper functions Bart Van Assche
2016-04-07 13:40   ` Christoph Hellwig
     [not found] ` <57055BC6.7070402-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-04-06 18:57   ` [PATCH 4/4] IB/srpt: Convert to percpu_ida tag allocation Bart Van Assche
2016-04-07 13:43     ` Christoph Hellwig
2016-04-07 23:03     ` Christoph Hellwig
2016-04-07 23:31       ` Nicholas A. Bellinger
2016-04-07 22:55   ` [PATCH] IB/srpt: Revert "Convert to percpu_ida tag allocation" Bart Van Assche
2016-04-07 23:37     ` Nicholas A. Bellinger
     [not found]       ` <1460072224.18732.67.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-07 23:44         ` Bart Van Assche
     [not found]           ` <5706F0E8.5020705-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-04-07 23:52             ` Nicholas A. Bellinger
     [not found]               ` <1460073123.18732.80.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-07 23:54                 ` Christoph Hellwig
2016-04-08  0:00                   ` Nicholas A. Bellinger
2016-04-08  0:00                 ` Doug Ledford
2016-04-07 23:49       ` Linus Torvalds
     [not found]         ` <CA+55aFwOnCeKzg4SuceZm98DgN-tV7aCdtrenAS93LP7GqrZtw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-07 23:56           ` Nicholas A. Bellinger
     [not found]             ` <1460073392.18732.83.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-08  0:13               ` Linus Torvalds
2016-04-07 22:29 ` [PATCH 0/4] IB/srpt and the percpu_ida conversion Nicholas A. Bellinger
     [not found]   ` <1460068181.18732.23.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-07 22:38     ` Bart Van Assche
2016-04-07 23:01   ` Christoph Hellwig [this message]
     [not found]     ` <20160407230110.GA9842-jcswGhMUV9g@public.gmane.org>
2016-04-07 23:24       ` Nicholas A. Bellinger
2016-04-07 23:34         ` Bart Van Assche
2016-04-07 23:47           ` Nicholas A. Bellinger
2016-04-07 23:49             ` Bart Van Assche
2016-04-08  8:16           ` Jack Wang
     [not found]         ` <1460071464.18732.57.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-07 23:47           ` Bart Van Assche

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=20160407230110.GA9842@lst.de \
    --to=hch@lst.de \
    --cc=bart.vanassche@sandisk.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=sagi@grimberg.me \
    --cc=target-devel@vger.kernel.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 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.