* New topic branch for block + gup work?
@ 2022-09-05 23:16 John Hubbard
2022-09-06 0:18 ` Jens Axboe
0 siblings, 1 reply; 2+ messages in thread
From: John Hubbard @ 2022-09-05 23:16 UTC (permalink / raw)
To: Jens Axboe, Andrew Morton, Logan Gunthorpe, Dan Williams,
Christoph Hellwig, Matthew Wilcox (Oracle)
Cc: LKML, linux-mm, linux-block, linux-fsdevel
Hi Jens,
After you suggested a topic branch [1] as a way to address the recent
bio_map_user_iov() conflict in linux-next, I've reviewed a few more
patchsets in mm, and am now starting to suspect that a topic branch
would be ideal here.
Logan's "Userspace P2PDMA with O_DIRECT NVMe devices" series [2], my
"convert most filesystems to pin_user_pages_fast()" series [3], and the
block layer change from [1], all conflict in iov_iter*, and in
bio_map_user_iov().
Less of an issue but still worth considering, Dan's "Fix the DAX-gup
mistake" series [4] conflicts in gup.c, too.
Maybe:
gup_bio
, or something like that, as a topic branch?
Everyone: thoughts, preferences here?
[1] https://lore.kernel.org/r/20220901161722.739d2013@canb.auug.org.au
[2] https://lore.kernel.org/r/20220825152425.6296-1-logang@deltatee.com
[3] https://lore.kernel.org/r/20220831041843.973026-1-jhubbard@nvidia.com
[4] https://lore.kernel.org/r/166225775968.2351842.11156458342486082012.stgit@dwillia2-xfh.jf.intel.com
thanks,
--
John Hubbard
NVIDIA
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: New topic branch for block + gup work?
2022-09-05 23:16 New topic branch for block + gup work? John Hubbard
@ 2022-09-06 0:18 ` Jens Axboe
0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2022-09-06 0:18 UTC (permalink / raw)
To: John Hubbard, Andrew Morton, Logan Gunthorpe, Dan Williams,
Christoph Hellwig, Matthew Wilcox (Oracle)
Cc: LKML, linux-mm, linux-block, linux-fsdevel
On 9/5/22 5:16 PM, John Hubbard wrote:
> Hi Jens,
>
> After you suggested a topic branch [1] as a way to address the recent
> bio_map_user_iov() conflict in linux-next, I've reviewed a few more
> patchsets in mm, and am now starting to suspect that a topic branch
> would be ideal here.
>
> Logan's "Userspace P2PDMA with O_DIRECT NVMe devices" series [2], my
> "convert most filesystems to pin_user_pages_fast()" series [3], and the
> block layer change from [1], all conflict in iov_iter*, and in
> bio_map_user_iov().
>
> Less of an issue but still worth considering, Dan's "Fix the DAX-gup
> mistake" series [4] conflicts in gup.c, too.
>
> Maybe:
>
> gup_bio
>
> , or something like that, as a topic branch?
>
> Everyone: thoughts, preferences here?
My suggestion would be to branch from for-6.1/block, then we can
apply the gup patches on top of that. I'd probably just call it
for-6.1/block-gup.
--
Jens Axboe
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-09-06 0:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-05 23:16 New topic branch for block + gup work? John Hubbard
2022-09-06 0:18 ` Jens Axboe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).