This framework is no longer used - so discard it.
Signed-off-by: NeilBrown
---
include/linux/backing-dev-defs.h |8 -
include/linux/backing-dev.h |2 -
include/trace/events/writeback.h | 28 ---
mm/backing-dev.c | 57 --
bfq_get_queue() expects a "bool" for the third arg, so pass "false"
rather than "BLK_RW_ASYNC" which will soon be removed.
Acked-by: Jens Axboe
Signed-off-by: NeilBrown
---
block/bfq-iosched.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/bfq-iosched.c b/block/bfq
As congestion is no longer tracked, congestion_wait() is effectively
equivalent to io_schedule_timeout().
So introduce f2fs_io_schedule_timeout() which sets TASK_UNINTERRUPTIBLE
and call that instead.
Signed-off-by: NeilBrown
---
fs/f2fs/compress.c |4 +---
fs/f2fs/data.c |3 +--
fs/
These functions are no longer useful as no BDIs report congestions any
more.
Removing the test on bdi_write_contested() in current_may_throttle()
could cause a small change in behaviour, but only when PF_LOCAL_THROTTLE
is set.
So replace the calls by 'false' and simplify the code - and remove the
inode_congested() reports if the backing-device for the inode is
congested. No bdi reports congestion any more, so this always
returns 'false'.
So remove inode_congested() and related functions, and remove the call
sites, assuming that inode_congested() always returns 'false'.
Signed-off-by: Nei
The bdi congestion tracking in not widely used and will be removed.
CEPHfs is one of a small number of filesystems that uses it, setting
just the async (write) congestion flags at what it determines are
appropriate times.
The only remaining effect of the async flag is to cause (some)
WB_SYNC_NONE
The bdi congestion tracking in not widely used and will be removed.
NFS is one of a small number of filesystems that uses it, setting just
the async (write) congestion flag at what it determines are appropriate
times.
The only remaining effect of the async flag is to cause (some)
WB_SYNC_NONE wri
The bdi congestion tracking in not widely used and will be removed.
Fuse is one of a small number of filesystems that uses it, setting both
the sync (read) and async (write) congestion flags at what it determines
are appropriate times.
The only remaining effect of the sync flag is to cause read-a
If ->readpages doesn't process all the pages, then it is best to act as
though they weren't requested so that a subsequent readahead can try
again.
So:
- remove any 'ahead' pages from the page cache so they can be loaded
with ->readahead() rather then multiple ->read()s
- update the file_ra
Here is another refresh of my "remove congestion tracking" series.
I removed the small tweaks to read-ahead code because they raised
questions and are actually required for this series.
Everything else is the same.
Andrew: please drop the version of this that is currently in your tree
even if yo
Add some "big-picture" documentation for read-ahead and polish the code
to make it fit this documentation.
The meaning of ->async_size is clarified to match its name.
i.e. Any request to ->readahead() has a sync part and an async part.
The caller will wait for the sync pages to complete, but will
Various DOC: sections in gfp.h have subsection headers (~~~) but the
place where they are included in mm-api.rst does not have section, only
chapters.
So convert to section headers (---) to avoid confusion. Specifically if
section are added later in mm-api.rst, an error results.
Signed-off-by: Ne
12 matches
Mail list logo