2005-04-17 02:20:36 +04:00
|
|
|
#
|
|
|
|
|
# Makefile for the Linux filesystems.
|
|
|
|
|
#
|
|
|
|
|
# 14 Sep 2000, Christoph Hellwig <hch@infradead.org>
|
|
|
|
|
# Rewritten to use lists instead of if-statements.
|
|
|
|
|
#
|
|
|
|
|
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-09-30 22:45:40 +04:00
|
|
|
obj-y := open.o read_write.o file_table.o super.o \
|
|
|
|
|
char_dev.o stat.o exec.o pipe.o namei.o fcntl.o \
|
2008-08-06 17:12:22 +04:00
|
|
|
ioctl.o readdir.o select.o fifo.o dcache.o inode.o \
|
2008-10-16 09:05:12 +04:00
|
|
|
attr.o bad_inode.o file.o filesystems.o namespace.o \
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-09-30 22:45:40 +04:00
|
|
|
seq_file.o xattr.o libfs.o fs-writeback.o \
|
2006-12-08 13:36:31 +03:00
|
|
|
pnode.o drop_caches.o splice.o sync.o utimes.o \
|
|
|
|
|
stack.o
|
[PATCH] BLOCK: Make it possible to disable the block layer [try #6]
Make it possible to disable the block layer. Not all embedded devices require
it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
the block layer to be present.
This patch does the following:
(*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
support.
(*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
an item that uses the block layer. This includes:
(*) Block I/O tracing.
(*) Disk partition code.
(*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.
(*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
block layer to do scheduling. Some drivers that use SCSI facilities -
such as USB storage - end up disabled indirectly from this.
(*) Various block-based device drivers, such as IDE and the old CDROM
drivers.
(*) MTD blockdev handling and FTL.
(*) JFFS - which uses set_bdev_super(), something it could avoid doing by
taking a leaf out of JFFS2's book.
(*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
however, still used in places, and so is still available.
(*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
parts of linux/fs.h.
(*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.
(*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.
(*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
is not enabled.
(*) fs/no-block.c is created to hold out-of-line stubs and things that are
required when CONFIG_BLOCK is not set:
(*) Default blockdev file operations (to give error ENODEV on opening).
(*) Makes some /proc changes:
(*) /proc/devices does not list any blockdevs.
(*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.
(*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.
(*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
given command other than Q_SYNC or if a special device is specified.
(*) In init/do_mounts.c, no reference is made to the blockdev routines if
CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.
(*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
error ENOSYS by way of cond_syscall if so).
(*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
CONFIG_BLOCK is not set, since they can't then happen.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2006-09-30 22:45:40 +04:00
|
|
|
|
|
|
|
|
ifeq ($(CONFIG_BLOCK),y)
|
|
|
|
|
obj-y += buffer.o bio.o block_dev.o direct-io.o mpage.o ioprio.o
|
|
|
|
|
else
|
|
|
|
|
obj-y += no-block.o
|
|
|
|
|
endif
|
2005-04-17 02:20:36 +04:00
|
|
|
|
2008-06-30 22:04:41 +04:00
|
|
|
obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o
|
[PATCH] inotify
inotify is intended to correct the deficiencies of dnotify, particularly
its inability to scale and its terrible user interface:
* dnotify requires the opening of one fd per each directory
that you intend to watch. This quickly results in too many
open files and pins removable media, preventing unmount.
* dnotify is directory-based. You only learn about changes to
directories. Sure, a change to a file in a directory affects
the directory, but you are then forced to keep a cache of
stat structures.
* dnotify's interface to user-space is awful. Signals?
inotify provides a more usable, simple, powerful solution to file change
notification:
* inotify's interface is a system call that returns a fd, not SIGIO.
You get a single fd, which is select()-able.
* inotify has an event that says "the filesystem that the item
you were watching is on was unmounted."
* inotify can watch directories or files.
Inotify is currently used by Beagle (a desktop search infrastructure),
Gamin (a FAM replacement), and other projects.
See Documentation/filesystems/inotify.txt.
Signed-off-by: Robert Love <rml@novell.com>
Cc: John McCutchan <ttb@tentacle.dhs.org>
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-07-13 01:06:03 +04:00
|
|
|
obj-$(CONFIG_INOTIFY) += inotify.o
|
2006-06-02 00:10:59 +04:00
|
|
|
obj-$(CONFIG_INOTIFY_USER) += inotify_user.o
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_EPOLL) += eventpoll.o
|
2007-05-11 09:23:11 +04:00
|
|
|
obj-$(CONFIG_ANON_INODES) += anon_inodes.o
|
signal/timer/event: signalfd core
This patch series implements the new signalfd() system call.
I took part of the original Linus code (and you know how badly it can be
broken :), and I added even more breakage ;) Signals are fetched from the same
signal queue used by the process, so signalfd will compete with standard
kernel delivery in dequeue_signal(). If you want to reliably fetch signals on
the signalfd file, you need to block them with sigprocmask(SIG_BLOCK). This
seems to be working fine on my Dual Opteron machine. I made a quick test
program for it:
http://www.xmailserver.org/signafd-test.c
The signalfd() system call implements signal delivery into a file descriptor
receiver. The signalfd file descriptor if created with the following API:
int signalfd(int ufd, const sigset_t *mask, size_t masksize);
The "ufd" parameter allows to change an existing signalfd sigmask, w/out going
to close/create cycle (Linus idea). Use "ufd" == -1 if you want a brand new
signalfd file.
The "mask" allows to specify the signal mask of signals that we are interested
in. The "masksize" parameter is the size of "mask".
The signalfd fd supports the poll(2) and read(2) system calls. The poll(2)
will return POLLIN when signals are available to be dequeued. As a direct
consequence of supporting the Linux poll subsystem, the signalfd fd can use
used together with epoll(2) too.
The read(2) system call will return a "struct signalfd_siginfo" structure in
the userspace supplied buffer. The return value is the number of bytes copied
in the supplied buffer, or -1 in case of error. The read(2) call can also
return 0, in case the sighand structure to which the signalfd was attached,
has been orphaned. The O_NONBLOCK flag is also supported, and read(2) will
return -EAGAIN in case no signal is available.
If the size of the buffer passed to read(2) is lower than sizeof(struct
signalfd_siginfo), -EINVAL is returned. A read from the signalfd can also
return -ERESTARTSYS in case a signal hits the process. The format of the
struct signalfd_siginfo is, and the valid fields depends of the (->code &
__SI_MASK) value, in the same way a struct siginfo would:
struct signalfd_siginfo {
__u32 signo; /* si_signo */
__s32 err; /* si_errno */
__s32 code; /* si_code */
__u32 pid; /* si_pid */
__u32 uid; /* si_uid */
__s32 fd; /* si_fd */
__u32 tid; /* si_fd */
__u32 band; /* si_band */
__u32 overrun; /* si_overrun */
__u32 trapno; /* si_trapno */
__s32 status; /* si_status */
__s32 svint; /* si_int */
__u64 svptr; /* si_ptr */
__u64 utime; /* si_utime */
__u64 stime; /* si_stime */
__u64 addr; /* si_addr */
};
[akpm@linux-foundation.org: fix signalfd_copyinfo() on i386]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 09:23:13 +04:00
|
|
|
obj-$(CONFIG_SIGNALFD) += signalfd.o
|
signal/timer/event: timerfd core
This patch introduces a new system call for timers events delivered though
file descriptors. This allows timer event to be used with standard POSIX
poll(2), select(2) and read(2). As a consequence of supporting the Linux
f_op->poll subsystem, they can be used with epoll(2) too.
The system call is defined as:
int timerfd(int ufd, int clockid, int flags, const struct itimerspec *utmr);
The "ufd" parameter allows for re-use (re-programming) of an existing timerfd
w/out going through the close/open cycle (same as signalfd). If "ufd" is -1,
s new file descriptor will be created, otherwise the existing "ufd" will be
re-programmed.
The "clockid" parameter is either CLOCK_MONOTONIC or CLOCK_REALTIME. The time
specified in the "utmr->it_value" parameter is the expiry time for the timer.
If the TFD_TIMER_ABSTIME flag is set in "flags", this is an absolute time,
otherwise it's a relative time.
If the time specified in the "utmr->it_interval" is not zero (.tv_sec == 0,
tv_nsec == 0), this is the period at which the following ticks should be
generated.
The "utmr->it_interval" should be set to zero if only one tick is requested.
Setting the "utmr->it_value" to zero will disable the timer, or will create a
timerfd without the timer enabled.
The function returns the new (or same, in case "ufd" is a valid timerfd
descriptor) file, or -1 in case of error.
As stated before, the timerfd file descriptor supports poll(2), select(2) and
epoll(2). When a timer event happened on the timerfd, a POLLIN mask will be
returned.
The read(2) call can be used, and it will return a u32 variable holding the
number of "ticks" that happened on the interface since the last call to
read(2). The read(2) call supportes the O_NONBLOCK flag too, and EAGAIN will
be returned if no ticks happened.
A quick test program, shows timerfd working correctly on my amd64 box:
http://www.xmailserver.org/timerfd-test.c
[akpm@linux-foundation.org: add sys_timerfd to sys_ni.c]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 09:23:16 +04:00
|
|
|
obj-$(CONFIG_TIMERFD) += timerfd.o
|
signal/timer/event: eventfd core
This is a very simple and light file descriptor, that can be used as event
wait/dispatch by userspace (both wait and dispatch) and by the kernel
(dispatch only). It can be used instead of pipe(2) in all cases where those
would simply be used to signal events. Their kernel overhead is much lower
than pipes, and they do not consume two fds. When used in the kernel, it can
offer an fd-bridge to enable, for example, functionalities like KAIO or
syslets/threadlets to signal to an fd the completion of certain operations.
But more in general, an eventfd can be used by the kernel to signal readiness,
in a POSIX poll/select way, of interfaces that would otherwise be incompatible
with it. The API is:
int eventfd(unsigned int count);
The eventfd API accepts an initial "count" parameter, and returns an eventfd
fd. It supports poll(2) (POLLIN, POLLOUT, POLLERR), read(2) and write(2).
The POLLIN flag is raised when the internal counter is greater than zero.
The POLLOUT flag is raised when at least a value of "1" can be written to the
internal counter.
The POLLERR flag is raised when an overflow in the counter value is detected.
The write(2) operation can never overflow the counter, since it blocks (unless
O_NONBLOCK is set, in which case -EAGAIN is returned).
But the eventfd_signal() function can do it, since it's supposed to not sleep
during its operation.
The read(2) function reads the __u64 counter value, and reset the internal
value to zero. If the value read is equal to (__u64) -1, an overflow happened
on the internal counter (due to 2^64 eventfd_signal() posts that has never
been retired - unlickely, but possible).
The write(2) call writes an __u64 count value, and adds it to the current
counter. The eventfd fd supports O_NONBLOCK also.
On the kernel side, we have:
struct file *eventfd_fget(int fd);
int eventfd_signal(struct file *file, unsigned int n);
The eventfd_fget() should be called to get a struct file* from an eventfd fd
(this is an fget() + check of f_op being an eventfd fops pointer).
The kernel can then call eventfd_signal() every time it wants to post an event
to userspace. The eventfd_signal() function can be called from any context.
An eventfd() simple test and bench is available here:
http://www.xmailserver.org/eventfd-bench.c
This is the eventfd-based version of pipetest-4 (pipe(2) based):
http://www.xmailserver.org/pipetest-4.c
Not that performance matters much in the eventfd case, but eventfd-bench
shows almost as double as performance than pipetest-4.
[akpm@linux-foundation.org: fix i386 build]
[akpm@linux-foundation.org: add sys_eventfd to sys_ni.c]
Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-11 09:23:19 +04:00
|
|
|
obj-$(CONFIG_EVENTFD) += eventfd.o
|
2008-10-16 09:05:12 +04:00
|
|
|
obj-$(CONFIG_AIO) += aio.o
|
2008-08-06 17:12:22 +04:00
|
|
|
obj-$(CONFIG_FILE_LOCKING) += locks.o
|
2006-01-10 07:52:14 +03:00
|
|
|
obj-$(CONFIG_COMPAT) += compat.o compat_ioctl.o
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
|
nfsd-$(CONFIG_NFSD) := nfsctl.o
|
|
|
|
|
obj-y += $(nfsd-y) $(nfsd-m)
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_BINFMT_AOUT) += binfmt_aout.o
|
|
|
|
|
obj-$(CONFIG_BINFMT_EM86) += binfmt_em86.o
|
|
|
|
|
obj-$(CONFIG_BINFMT_MISC) += binfmt_misc.o
|
|
|
|
|
|
|
|
|
|
# binfmt_script is always there
|
|
|
|
|
obj-y += binfmt_script.o
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_BINFMT_ELF) += binfmt_elf.o
|
2008-01-30 15:31:46 +03:00
|
|
|
obj-$(CONFIG_COMPAT_BINFMT_ELF) += compat_binfmt_elf.o
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_BINFMT_ELF_FDPIC) += binfmt_elf_fdpic.o
|
|
|
|
|
obj-$(CONFIG_BINFMT_SOM) += binfmt_som.o
|
|
|
|
|
obj-$(CONFIG_BINFMT_FLAT) += binfmt_flat.o
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_FS_MBCACHE) += mbcache.o
|
|
|
|
|
obj-$(CONFIG_FS_POSIX_ACL) += posix_acl.o xattr_acl.o
|
2005-06-22 21:16:26 +04:00
|
|
|
obj-$(CONFIG_NFS_COMMON) += nfs_common/
|
2006-09-29 13:01:34 +04:00
|
|
|
obj-$(CONFIG_GENERIC_ACL) += generic_acl.o
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
|
obj-$(CONFIG_QUOTA) += dquot.o
|
|
|
|
|
obj-$(CONFIG_QFMT_V1) += quota_v1.o
|
|
|
|
|
obj-$(CONFIG_QFMT_V2) += quota_v2.o
|
|
|
|
|
obj-$(CONFIG_QUOTACTL) += quota.o
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_DNOTIFY) += dnotify.o
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_PROC_FS) += proc/
|
|
|
|
|
obj-y += partitions/
|
|
|
|
|
obj-$(CONFIG_SYSFS) += sysfs/
|
2006-05-03 22:38:53 +04:00
|
|
|
obj-$(CONFIG_CONFIGFS_FS) += configfs/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-y += devpts/
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_PROFILING) += dcookies.o
|
2006-01-18 12:30:29 +03:00
|
|
|
obj-$(CONFIG_DLM) += dlm/
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
|
# Do not add any filesystems before this line
|
|
|
|
|
obj-$(CONFIG_REISERFS_FS) += reiserfs/
|
|
|
|
|
obj-$(CONFIG_EXT3_FS) += ext3/ # Before ext2 so root fs can be ext3
|
2008-10-17 23:03:38 +04:00
|
|
|
obj-$(CONFIG_EXT4_FS) += ext4/ # Before ext2 so root fs can be ext4
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_JBD) += jbd/
|
2006-10-11 12:21:01 +04:00
|
|
|
obj-$(CONFIG_JBD2) += jbd2/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_EXT2_FS) += ext2/
|
|
|
|
|
obj-$(CONFIG_CRAMFS) += cramfs/
|
2007-10-17 10:29:27 +04:00
|
|
|
obj-y += ramfs/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_HUGETLBFS) += hugetlbfs/
|
|
|
|
|
obj-$(CONFIG_CODA_FS) += coda/
|
|
|
|
|
obj-$(CONFIG_MINIX_FS) += minix/
|
|
|
|
|
obj-$(CONFIG_FAT_FS) += fat/
|
|
|
|
|
obj-$(CONFIG_BFS_FS) += bfs/
|
|
|
|
|
obj-$(CONFIG_ISO9660_FS) += isofs/
|
|
|
|
|
obj-$(CONFIG_HFSPLUS_FS) += hfsplus/ # Before hfs to find wrapped HFS+
|
|
|
|
|
obj-$(CONFIG_HFS_FS) += hfs/
|
2006-10-04 13:16:22 +04:00
|
|
|
obj-$(CONFIG_ECRYPT_FS) += ecryptfs/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_VXFS_FS) += freevxfs/
|
|
|
|
|
obj-$(CONFIG_NFS_FS) += nfs/
|
|
|
|
|
obj-$(CONFIG_EXPORTFS) += exportfs/
|
|
|
|
|
obj-$(CONFIG_NFSD) += nfsd/
|
|
|
|
|
obj-$(CONFIG_LOCKD) += lockd/
|
|
|
|
|
obj-$(CONFIG_NLS) += nls/
|
|
|
|
|
obj-$(CONFIG_SYSV_FS) += sysv/
|
|
|
|
|
obj-$(CONFIG_SMB_FS) += smbfs/
|
|
|
|
|
obj-$(CONFIG_CIFS) += cifs/
|
|
|
|
|
obj-$(CONFIG_NCP_FS) += ncpfs/
|
|
|
|
|
obj-$(CONFIG_HPFS_FS) += hpfs/
|
|
|
|
|
obj-$(CONFIG_NTFS_FS) += ntfs/
|
|
|
|
|
obj-$(CONFIG_UFS_FS) += ufs/
|
|
|
|
|
obj-$(CONFIG_EFS_FS) += efs/
|
|
|
|
|
obj-$(CONFIG_JFFS2_FS) += jffs2/
|
2008-07-14 20:08:38 +04:00
|
|
|
obj-$(CONFIG_UBIFS_FS) += ubifs/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_AFFS_FS) += affs/
|
|
|
|
|
obj-$(CONFIG_ROMFS_FS) += romfs/
|
|
|
|
|
obj-$(CONFIG_QNX4FS_FS) += qnx4/
|
|
|
|
|
obj-$(CONFIG_AUTOFS_FS) += autofs/
|
|
|
|
|
obj-$(CONFIG_AUTOFS4_FS) += autofs4/
|
|
|
|
|
obj-$(CONFIG_ADFS_FS) += adfs/
|
2005-09-10 00:10:22 +04:00
|
|
|
obj-$(CONFIG_FUSE_FS) += fuse/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_UDF_FS) += udf/
|
|
|
|
|
obj-$(CONFIG_SUN_OPENPROMFS) += openpromfs/
|
2008-07-26 06:45:17 +04:00
|
|
|
obj-$(CONFIG_OMFS_FS) += omfs/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_JFS_FS) += jfs/
|
|
|
|
|
obj-$(CONFIG_XFS_FS) += xfs/
|
[PATCH] v9fs: Documentation, Makefiles, Configuration
OVERVIEW
V9FS is a distributed file system for Linux which provides an
implementation of the Plan 9 resource sharing protocol 9P. It can be
used to share all sorts of resources: static files, synthetic file servers
(such as /proc or /sys), devices, and application file servers (such as
FUSE).
BACKGROUND
Plan 9 (http://plan9.bell-labs.com/plan9) is a research operating
system and associated applications suite developed by the Computing
Science Research Center of AT&T Bell Laboratories (now a part of
Lucent Technologies), the same group that developed UNIX , C, and C++.
Plan 9 was initially released in 1993 to universities, and then made
generally available in 1995. Its core operating systems code laid the
foundation for the Inferno Operating System released as a product by
Lucent Bell-Labs in 1997. The Inferno venture was the only commercial
embodiment of Plan 9 and is currently maintained as a product by Vita
Nuova (http://www.vitanuova.com). After updated releases in 2000 and
2002, Plan 9 was open-sourced under the OSI approved Lucent Public
License in 2003.
The Plan 9 project was started by Ken Thompson and Rob Pike in 1985.
Their intent was to explore potential solutions to some of the
shortcomings of UNIX in the face of the widespread use of high-speed
networks to connect machines. In UNIX, networking was an afterthought
and UNIX clusters became little more than a network of stand-alone
systems. Plan 9 was designed from first principles as a seamless
distributed system with integrated secure network resource sharing.
Applications and services were architected in such a way as to allow
for implicit distribution across a cluster of systems. Configuring an
environment to use remote application components or services in place
of their local equivalent could be achieved with a few simple command
line instructions. For the most part, application implementations
operated independent of the location of their actual resources.
Commercial operating systems haven't changed much in the 20 years
since Plan 9 was conceived. Network and distributed systems support is
provided by a patchwork of middle-ware, with an endless number of
packages supplying pieces of the puzzle. Matters are complicated by
the use of different complicated protocols for individual services,
and separate implementations for kernel and application resources.
The V9FS project (http://v9fs.sourceforge.net) is an attempt to bring
Plan 9's unified approach to resource sharing to Linux and other
operating systems via support for the 9P2000 resource sharing
protocol.
V9FS HISTORY
V9FS was originally developed by Ron Minnich and Maya Gokhale at Los
Alamos National Labs (LANL) in 1997. In November of 2001, Greg Watson
setup a SourceForge project as a public repository for the code which
supported the Linux 2.4 kernel.
About a year ago, I picked up the initial attempt Ron Minnich had
made to provide 2.6 support and got the code integrated into a 2.6.5
kernel. I then went through a line-for-line re-write attempting to
clean-up the code while more closely following the Linux Kernel style
guidelines. I co-authored a paper with Ron Minnich on the V9FS Linux
support including performance comparisons to NFSv3 using Bonnie and
PostMark - this paper appeared at the USENIX/FREENIX 2005
conference in April 2005:
( http://www.usenix.org/events/usenix05/tech/freenix/hensbergen.html ).
CALL FOR PARTICIPATION/REQUEST FOR COMMENTS
Our 2.6 kernel support is stabilizing and we'd like to begin pursuing
its integration into the official kernel tree. We would appreciate any
review, comments, critiques, and additions from this community and are
actively seeking people to join our project and help us produce
something that would be acceptable and useful to the Linux community.
STATUS
The code is reasonably stable, although there are no doubt corner cases
our regression tests haven't discovered yet. It is in regular use by several
of the developers and has been tested on x86 and PowerPC
(32-bit and 64-bit) in both small and large (LANL cluster) deployments.
Our current regression tests include fsx, bonnie, and postmark.
It was our intention to keep things as simple as possible for this
release -- trying to focus on correctness within the core of the
protocol support versus a rich set of features. For example: a more
complete security model and cache layer are in the road map, but
excluded from this release. Additionally, we have removed support for
mmap operations at Al Viro's request.
PERFORMANCE
Detailed performance numbers and analysis are included in the FREENIX
paper, but we show comparable performance to NFSv3 for large file
operations based on the Bonnie benchmark, and superior performance for
many small file operations based on the PostMark benchmark. Somewhat
preliminary graphs (from the FREENIX paper) are available
(http://v9fs.sourceforge.net/perf/index.html).
RESOURCES
The source code is available in a few different forms:
tarballs: http://v9fs.sf.net
CVSweb: http://cvs.sourceforge.net/viewcvs.py/v9fs/linux-9p/
CVS: :pserver:anonymous@cvs.sourceforge.net:/cvsroot/v9fs/linux-9p
Git: rsync://v9fs.graverobber.org/v9fs (webgit: http://v9fs.graverobber.org)
9P: tcp!v9fs.graverobber.org!6564
The user-level server is available from either the Plan 9 distribution
or from http://v9fs.sf.net
Other support applications are still being developed, but preliminary
version can be downloaded from sourceforge.
Documentation on the protocol has historically been the Plan 9 Man
pages (http://plan9.bell-labs.com/sys/man/5/INDEX.html), but there is
an effort under way to write a more complete Internet-Draft style
specification (http://v9fs.sf.net/rfc).
There are a couple of mailing lists supporting v9fs, but the most used
is v9fs-developer@lists.sourceforge.net -- please direct/cc your
comments there so the other v9fs contibutors can participate in the
conversation. There is also an IRC channel: irc://freenode.net/#v9fs
This part of the patch contains Documentation, Makefiles, and configuration
file changes.
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-10 00:04:18 +04:00
|
|
|
obj-$(CONFIG_9P_FS) += 9p/
|
2005-04-17 02:20:36 +04:00
|
|
|
obj-$(CONFIG_AFS_FS) += afs/
|
|
|
|
|
obj-$(CONFIG_BEFS_FS) += befs/
|
|
|
|
|
obj-$(CONFIG_HOSTFS) += hostfs/
|
|
|
|
|
obj-$(CONFIG_HPPFS) += hppfs/
|
|
|
|
|
obj-$(CONFIG_DEBUG_FS) += debugfs/
|
2005-12-16 01:31:24 +03:00
|
|
|
obj-$(CONFIG_OCFS2_FS) += ocfs2/
|
2006-01-16 19:43:37 +03:00
|
|
|
obj-$(CONFIG_GFS2_FS) += gfs2/
|
