summaryrefslogtreecommitdiffstats
path: root/net/bridge/br_if.c
diff options
context:
space:
mode:
authorAnton Altaparmakov <aia21@cantab.net>2005-10-11 15:40:40 +0100
committerAnton Altaparmakov <aia21@cantab.net>2005-10-11 15:40:40 +0100
commit98b270362bb9ea6629732e7f5b65b8a6ce4743c7 (patch)
tree2ca1f46a426628a16cc8cef2a4d4fba657d7ac1f /net/bridge/br_if.c
parent29f5f3c141c58b0a4c0765c77da612271875bcce (diff)
downloadop-kernel-dev-98b270362bb9ea6629732e7f5b65b8a6ce4743c7.zip
op-kernel-dev-98b270362bb9ea6629732e7f5b65b8a6ce4743c7.tar.gz
NTFS: The big ntfs write(2) rewrite has arrived. We now implement our own
file operations ->write(), ->aio_write(), and ->writev() for regular files. This replaces the old use of generic_file_write(), et al and the address space operations ->prepare_write and ->commit_write. This means that both sparse and non-sparse (unencrypted and uncompressed) files can now be extended using the normal write(2) code path. There are two limitations at present and these are that we never create sparse files and that we only have limited support for highly fragmented files, i.e. ones whose data attribute is split across multiple extents. When such a case is encountered, EOPNOTSUPP is returned. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
Diffstat (limited to 'net/bridge/br_if.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud