From: Jason Gunthorpe <jgg@ziepe•ca>
To: David Ahern <dsahern@gmail•com>
Cc: Leon Romanovsky <leon@kernel•org>,
stephen@networkplumber•org,
Steve Wise <swise@opengridcomputing•com>,
netdev@vger•kernel.org, linux-rdma@vger•kernel.org
Subject: Re: [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking
Date: Tue, 13 Mar 2018 15:13:55 -0600 [thread overview]
Message-ID: <20180313211355.GD21498@ziepe.ca> (raw)
In-Reply-To: <dde7cc61-22af-b589-348f-e91c6657a289@gmail.com>
On Tue, Mar 13, 2018 at 01:45:12PM -0700, David Ahern wrote:
> On 3/13/18 1:32 AM, Leon Romanovsky wrote:
> > On Mon, Mar 12, 2018 at 10:53:03AM -0700, David Ahern wrote:
> >> On 3/12/18 8:16 AM, Steve Wise wrote:
> >>> Hey all,
> >>>
> >>> The kernel side of this series has been merged for rdma-next [1]. Let me
> >>> know if this iproute2 series can be merged, of if it needs more changes.
> >>>
> >>
> >> The problem is that iproute2 headers are synced to kernel headers from
> >> DaveM's tree (net-next mainly). I take it this series will not appear in
> >> Dave's tree until after a merge through Linus' tree. Correct?
> >
> > David,
> >
> > Technically, you are right, and we would like to ask you for an extra tweak
> > to the flow for the RDMAtool, because current scheme causes delays at least
> > cycle.
> >
> > Every RDMAtool's patchset which requires changes to headers is always
> > includes header patch, can you please accept those series and once you
> > are bringing new net-next headers from Linus, simply overwrite all our
> > headers?
>
> I did not follow the discussion back when this decision was made, so how
> did rdma tool end up in iproute2? I do not need the overhead of
> sometimes I sync the rdma header file and sometimes I don't.
Could you pull the uapi headers from linux-next? That tree will have
both netdev and rdma stuff merged together properly.
Jason
next prev parent reply other threads:[~2018-03-13 21:13 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 19:55 [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking Steve Wise
2018-02-27 16:06 ` [PATCH v2 iproute2-next 1/6] rdma: update rdma_netlink.h Steve Wise
2018-02-27 16:07 ` [PATCH v2 iproute2-next 2/6] rdma: initialize the rd struct Steve Wise
2018-03-13 18:11 ` Leon Romanovsky
2018-02-27 16:07 ` [PATCH v2 iproute2-next 3/6] rdma: Add CM_ID resource tracking information Steve Wise
2018-03-13 18:07 ` Leon Romanovsky
2018-03-13 19:44 ` Steve Wise
2018-03-26 14:17 ` David Ahern
2018-03-26 14:30 ` Steve Wise
2018-03-26 14:44 ` David Ahern
2018-03-26 14:55 ` Steve Wise
2018-03-26 15:08 ` Leon Romanovsky
2018-03-26 15:24 ` Steve Wise
2018-03-26 17:06 ` Leon Romanovsky
2018-03-26 17:13 ` Steve Wise
2018-03-26 17:27 ` Leon Romanovsky
2018-03-26 21:15 ` Jason Gunthorpe
2018-03-26 21:34 ` Steve Wise
2018-03-26 22:30 ` Jason Gunthorpe
2018-03-27 3:21 ` Leon Romanovsky
2018-03-27 14:44 ` Jason Gunthorpe
2018-03-27 15:15 ` Leon Romanovsky
2018-03-27 15:23 ` Jason Gunthorpe
2018-03-27 15:45 ` Steve Wise
2018-03-27 16:01 ` Leon Romanovsky
2018-03-27 16:20 ` Steve Wise
2018-03-27 16:30 ` Leon Romanovsky
2018-03-27 16:38 ` Steve Wise
2018-03-26 15:40 ` David Ahern
2018-03-26 19:55 ` Steve Wise
2018-02-27 16:07 ` [PATCH v2 iproute2-next 4/6] rdma: Add CQ " Steve Wise
2018-03-13 19:05 ` Leon Romanovsky
2018-02-27 16:07 ` [PATCH v2 iproute2-next 5/6] rdma: Add MR " Steve Wise
2018-03-13 19:06 ` Leon Romanovsky
2018-02-27 16:07 ` [PATCH v2 iproute2-next 6/6] rdma: Add PD " Steve Wise
2018-03-13 19:07 ` Leon Romanovsky
2018-03-12 15:16 ` [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking Steve Wise
2018-03-12 17:53 ` David Ahern
2018-03-12 18:43 ` Steve Wise
2018-03-13 8:32 ` Leon Romanovsky
2018-03-13 20:45 ` David Ahern
2018-03-13 20:58 ` Doug Ledford
2018-03-16 16:18 ` David Ahern
2018-03-20 17:21 ` Doug Ledford
2018-03-21 16:59 ` David Ahern
2018-03-22 20:20 ` Steve Wise
2018-03-22 20:26 ` David Ahern
2018-03-13 21:13 ` Jason Gunthorpe [this message]
2018-03-15 3:14 ` David Ahern
2018-03-15 3:29 ` Jason Gunthorpe
2018-03-16 16:08 ` David Ahern
2018-03-16 16:23 ` Leon Romanovsky
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=20180313211355.GD21498@ziepe.ca \
--to=jgg@ziepe$(echo .)ca \
--cc=dsahern@gmail$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
--cc=swise@opengridcomputing$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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