[linux.git] / fs / ramfs / file-mmu.c

/* file-mmu.c: ramfs MMU-based file operations
 *
 * Resizable simple ram filesystem for Linux.
 *
 * Copyright (C) 2000 Linus Torvalds.
 *               2000 Transmeta Corp.
 *
 * Usage limits added by David Gibson, Linuxcare Australia.
 * This file is released under the GPL.
 */

/*
 * NOTE! This filesystem is probably most useful
 * not as a real filesystem, but as an example of
 * how virtual filesystems can be written.
 *
 * It doesn't get much simpler than this. Consider
 * that this file implements the full semantics of
 * a POSIX-compliant read-write filesystem.
 *
 * Note in particular how the filesystem does not
 * need to implement any data structures of its own
 * to keep track of the virtual data: using the VFS
 * caches is sufficient.
 */

#include <linux/fs.h>

const struct address_space_operations ramfs_aops = {
	.readpage	= simple_readpage,
	.prepare_write	= simple_prepare_write,
	.commit_write	= simple_commit_write
};

const struct file_operations ramfs_file_operations = {
	.read		= do_sync_read,
	.aio_read	= generic_file_aio_read,
	.write		= do_sync_write,
	.aio_write	= generic_file_aio_write,
	.mmap		= generic_file_mmap,
	.fsync		= simple_sync_file,
	.sendfile	= generic_file_sendfile,
	.llseek		= generic_file_llseek,
};

struct inode_operations ramfs_file_inode_operations = {
	.getattr	= simple_getattr,
};
Commit	Line	Data
642fb4d1 DH	1	/* file-mmu.c: ramfs MMU-based file operations
	2	*
	3	* Resizable simple ram filesystem for Linux.
	4	*
	5	* Copyright (C) 2000 Linus Torvalds.
	6	* 2000 Transmeta Corp.
	7	*
	8	* Usage limits added by David Gibson, Linuxcare Australia.
	9	* This file is released under the GPL.
	10	*/
	11
	12	/*
	13	* NOTE! This filesystem is probably most useful
	14	* not as a real filesystem, but as an example of
	15	* how virtual filesystems can be written.
	16	*
	17	* It doesn't get much simpler than this. Consider
	18	* that this file implements the full semantics of
	19	* a POSIX-compliant read-write filesystem.
	20	*
	21	* Note in particular how the filesystem does not
	22	* need to implement any data structures of its own
	23	* to keep track of the virtual data: using the VFS
	24	* caches is sufficient.
	25	*/
	26
642fb4d1	27	#include <linux/fs.h>
642fb4d1	28
f5e54d6e	29	const struct address_space_operations ramfs_aops = {
642fb4d1 DH	30	.readpage = simple_readpage,
	31	.prepare_write = simple_prepare_write,
	32	.commit_write = simple_commit_write
	33	};
	34
4b6f5d20	35	const struct file_operations ramfs_file_operations = {
543ade1f BP	36	.read = do_sync_read,
	37	.aio_read = generic_file_aio_read,
	38	.write = do_sync_write,
	39	.aio_write = generic_file_aio_write,
642fb4d1 DH	40	.mmap = generic_file_mmap,
	41	.fsync = simple_sync_file,
	42	.sendfile = generic_file_sendfile,
	43	.llseek = generic_file_llseek,
	44	};
	45
	46	struct inode_operations ramfs_file_inode_operations = {
	47	.getattr = simple_getattr,
	48	};