summaryrefslogtreecommitdiffstats
path: root/drivers/dma
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2014-02-03 14:09:13 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-02-07 15:52:48 -0800
commit4d3773c4bb41ed5228f1ab7a4a52b79e17b10515 (patch)
tree71c30d7009b36d22e9aab816f3dc7e373bb5f1e9 /drivers/dma
parentd35258ef702cca0c4e66d799f8e38b78c02ce8a5 (diff)
downloadop-kernel-dev-4d3773c4bb41ed5228f1ab7a4a52b79e17b10515.zip
op-kernel-dev-4d3773c4bb41ed5228f1ab7a4a52b79e17b10515.tar.gz
kernfs: implement kernfs_ops->atomic_write_len
A write to a kernfs_node is buffered through a kernel buffer. Writes <= PAGE_SIZE are performed atomically, while larger ones are executed in PAGE_SIZE chunks. While this is enough for sysfs, cgroup which is scheduled to be converted to use kernfs needs a bit more control over it. This patch adds kernfs_ops->atomic_write_len. If not set (zero), the behavior stays the same. If set, writes upto the size are executed atomically and larger writes are rejected with -E2BIG. A different implementation strategy would be allowing configuring chunking size while making the original write size available to the write method; however, such strategy, while being more complicated, doesn't really buy anything. If the write implementation has to handle chunking, the specific chunk size shouldn't matter all that much. Signed-off-by: Tejun Heo <tj@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/dma')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud