On Fri, Mar 11, 2022 at 08:43:24AM -0800, Luis Chamberlain wrote: > On Thu, Mar 10, 2022 at 03:35:02PM +0530, Kanchan Joshi wrote: > > On Thu, Mar 10, 2022 at 1:59 PM Christoph Hellwig <hch@xxxxxx> wrote: > > > > > > What branch is this against? > > Sorry I missed that in the cover. > > Two options - > > (a) https://urldefense.com/v3/__https://protect2.fireeye.com/v1/url?k=03500d22-5ccb341f-0351866d-0cc47a31309a-6f95e6932e414a1d&q=1&e=4ca7b05e-2fe6-40d9-bbcf-a4ed687eca9f&u=https*3A*2F*2Fgit.kernel.dk*2Fcgit*2Flinux-block*2Flog*2F*3Fh*3Dio_uring-big-sqe__;JSUlJSUlJSUl!!EwVzqGoTKBqv-0DWAJBm!FujuZ927K3fuIklgYjkWtodmdQnQyBqOw4Ge4M08DU_0oD5tPm0-wS2SZg0MDh8_2-U9$ > > first patch ("128 byte sqe support") is already there. > > (b) for-next (linux-block), series will fit on top of commit 9e9d83faa > > ("io_uring: Remove unneeded test in io_run_task_work_sig") > > > > > Do you have a git tree available? > > Not at the moment. > > > > @Jens: Please see if it is possible to move patches to your > > io_uring-big-sqe branch (and maybe rename that to big-sqe-pt.v1). > > Since Jens might be busy, I've put up a tree with all this stuff: > > https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/log/?h=20220311-io-uring-cmd__;!!EwVzqGoTKBqv-0DWAJBm!FujuZ927K3fuIklgYjkWtodmdQnQyBqOw4Ge4M08DU_0oD5tPm0-wS2SZg0MDiTF0Q7F$ > > It is based on option (b) mentioned above, I took linux-block for-next > and reset the tree to commit "io_uring: Remove unneeded test in > io_run_task_work_sig" before applying the series. FYI I can be involved in testing this and have added some colleagues that can help in this regard. We have been using some form of this work for several months now and haven't had any issues. That being said some simple tests I have are not currently working with the above git tree :). I will work to get this resolved and post an update here. > > Luis
