summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2022-07-04 14:42:04 +0300
committerDavid Sterba <dsterba@suse.com>2022-07-25 18:45:40 +0300
commitac5e666951507ceb1da2ed85c4f5c7bb88bec06e (patch)
tree75ee947458c6cb247605b2b9e3561812f6cf28e0 /tools/perf/scripts/python
parent8bfc9b2cf468c37870b980a16c345c9ba3a2010a (diff)
downloadlinux-ac5e666951507ceb1da2ed85c4f5c7bb88bec06e.tar.xz
btrfs: don't fallback to buffered IO for NOWAIT direct IO writes
Currently, for a direct IO write, if we need to fallback to buffered IO, either to satisfy the whole write operation or just a part of it, we do it in the current context even if it's a NOWAIT context. This is not ideal because we currently don't have support for NOWAIT semantics in the buffered IO path (we can block for several reasons), so we should instead return -EAGAIN to the caller, so that it knows it should retry (the whole operation or what's left of it) in a context where blocking is acceptable. Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions