From mboxrd@z Thu Jan 1 00:00:00 1970 From: joseph.r.gruher@intel.com (Gruher, Joseph R) Date: Fri, 12 May 2017 19:20:32 +0000 Subject: Unexpected issues with 2 NVME initiators using the same target In-Reply-To: References: <08131a05-1f56-ef61-990a-7fff04eea095@gmail.com> <1848296658.37025722.1487782361271.JavaMail.zimbra@redhat.com> <1554c1d1-6bf4-9ca2-12d4-a0125d8c5715@gmail.com> <3eb5814f-14cb-2b94-adf8-335d4b2eb7e9@grimberg.me> <26912d0c-578f-26e9-490d-94fc95bdf259@mellanox.com> <809f87ab-b787-9d40-5840-07500d12e81a@mellanox.com> <1948057100.362217696.1491824459274.JavaMail.zimbra@kalray.eu> <33e2cc35-f147-d4a4-9a42-8f1245e35842@mellanox.com> <517fb6d2-a010-1926-b4cb-0e6041722c28@grimberg.me> Message-ID: > >> Can we get it to 4.12 please (we need you to send it out today). > > > > Sagi, > > we are preparing a cap bit for it. > > I'll send it as soon as it will be ready (otherwise we'll add fence > > for devices that can handle without it - such as ConnectX5). > > Why? can't you just get what you have as a fix and incrementally add the > optimization for CX5? Any update here? Would love to be able to load up the new kernels without patching them every time. :)