search for: dio_refill_pages

Displaying 4 results from an estimated 4 matches for "dio_refill_pages".

2019 Jul 29
2
[PATCH 03/12] block: bio_release_pages: use flags arg instead of bool
On Tue, Jul 23, 2019 at 10:30:53PM -0700, Christoph Hellwig wrote: > On Tue, Jul 23, 2019 at 09:25:09PM -0700, john.hubbard at gmail.com wrote: > > From: John Hubbard <jhubbard at nvidia.com> > > > > In commit d241a95f3514 ("block: optionally mark pages dirty in > > bio_release_pages"), new "bool mark_dirty" argument was added to > >
2019 Jul 29
2
[PATCH 03/12] block: bio_release_pages: use flags arg instead of bool
On Tue, Jul 23, 2019 at 10:30:53PM -0700, Christoph Hellwig wrote: > On Tue, Jul 23, 2019 at 09:25:09PM -0700, john.hubbard at gmail.com wrote: > > From: John Hubbard <jhubbard at nvidia.com> > > > > In commit d241a95f3514 ("block: optionally mark pages dirty in > > bio_release_pages"), new "bool mark_dirty" argument was added to > >
2019 Jul 30
0
[PATCH 03/12] block: bio_release_pages: use flags arg instead of bool
...just for the fun of it :) Well, the point is _should_ not necessarily do. iomap_dio_zero adds the ZERO_PAGE, which we by definition don't need to refcount. So we can mark this bio BIO_NO_PAGE_REF safely after removing the get_page there. Note that the equivalent in the old direct I/O code, dio_refill_pages, will be a little more complicated as it can match user pages and the ZERO_PAGE in a single bio, so a per-bio flag won't handle it easily. Maybe we just need to use a separate bio there as well. In general with series like this we should not encode the status quo an pile new hacks upon the old...
2019 Jul 30
1
[PATCH 03/12] block: bio_release_pages: use flags arg instead of bool
...; > Well, the point is _should_ not necessarily do. iomap_dio_zero adds the > ZERO_PAGE, which we by definition don't need to refcount. So we can > mark this bio BIO_NO_PAGE_REF safely after removing the get_page there. > > Note that the equivalent in the old direct I/O code, dio_refill_pages, > will be a little more complicated as it can match user pages and the > ZERO_PAGE in a single bio, so a per-bio flag won't handle it easily. > Maybe we just need to use a separate bio there as well. > > In general with series like this we should not encode the status quo an &g...