Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit f81b691a authored by Ingo Molnar's avatar Ingo Molnar
Browse files

Merge commit 'v2.6.27-rc6' into x86/pat

parents 110e0358 adee14b2

Documentation/ABI/testing/sysfs-firmware-sgi_uv

0 → 100644
+27 −0
Original line number Original line Diff line number Diff line 
What:		/sys/firmware/sgi_uv/

Date:		August 2008

Contact:	Russ Anderson <rja@sgi.com>

Description:

		The /sys/firmware/sgi_uv directory contains information

		about the SGI UV platform.



		Under that directory are a number of files:



			partition_id

			coherence_id



		The partition_id entry contains the partition id.

		SGI UV systems can be partitioned into multiple physical

		machines, which each partition running a unique copy

		of the operating system.  Each partition will have a unique

		partition id.  To display the partition id, use the command:



			cat /sys/firmware/sgi_uv/partition_id



		The coherence_id entry contains the coherence id.

		A partitioned SGI UV system can have one or more coherence

		domain.  The coherence id indicates which coherence domain

		this partition is in.  To display the coherence id, use the

		command:



			cat /sys/firmware/sgi_uv/coherence_id

Documentation/dontdiff

+2 −0
Original line number Original line Diff line number Diff line
@@ -5,6 +5,8 @@ 
*.css

*.css

*.dvi

*.dvi

*.eps

*.eps

*.fw.gen.S

*.fw

*.gif

*.gif

*.grep

*.grep

*.grp

*.grp

Documentation/filesystems/Locking

+4 −11
Original line number Original line Diff line number Diff line
@@ -144,8 +144,8 @@ prototypes: 
	void (*kill_sb) (struct super_block *);

	void (*kill_sb) (struct super_block *);

locking rules:

locking rules:

		may block	BKL

		may block	BKL

get_sb		yes		yes

get_sb		yes		no

kill_sb		yes		yes

kill_sb		yes		no





->get_sb() returns error or 0 with locked superblock attached to the vfsmount

->get_sb() returns error or 0 with locked superblock attached to the vfsmount

(exclusive on ->s_umount).

(exclusive on ->s_umount).
@@ -409,12 +409,12 @@ ioctl: yes (see below) 
unlocked_ioctl:		no	(see below)

unlocked_ioctl:		no	(see below)

compat_ioctl:		no

compat_ioctl:		no

mmap:			no

mmap:			no

open:			maybe	(see below)

open:			no

flush:			no

flush:			no

release:		no

release:		no

fsync:			no	(see below)

fsync:			no	(see below)

aio_fsync:		no

aio_fsync:		no

fasync:			yes	(see below)

fasync:			no

lock:			yes

lock:			yes

readv:			no

readv:			no

writev:			no

writev:			no
@@ -431,13 +431,6 @@ For many filesystems, it is probably safe to acquire the inode 
semaphore.  Note some filesystems (i.e. remote ones) provide no

semaphore.  Note some filesystems (i.e. remote ones) provide no

protection for i_size so you will need to use the BKL.

protection for i_size so you will need to use the BKL.





->open() locking is in-transit: big lock partially moved into the methods.

The only exception is ->open() in the instances of file_operations that never

end up in ->i_fop/->proc_fops, i.e. ones that belong to character devices

(chrdev_open() takes lock before replacing ->f_op and calling the secondary

method. As soon as we fix the handling of module reference counters all

instances of ->open() will be called without the BKL.



Note: ext2_release() was *the* source of contention on fs-intensive

Note: ext2_release() was *the* source of contention on fs-intensive

loads and dropping BKL on ->release() helps to get rid of that (we still

loads and dropping BKL on ->release() helps to get rid of that (we still

grab BKL for cases when we close a file that had been opened r/w, but that

grab BKL for cases when we close a file that had been opened r/w, but that

Documentation/filesystems/ext4.txt

+6 −0
Original line number Original line Diff line number Diff line
@@ -26,6 +26,12 @@ Mailing list: linux-ext4@vger.kernel.org 




    git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git

    git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git





  - Note that it is highly important to install the mke2fs.conf file

    that comes with the e2fsprogs 1.41.x sources in /etc/mke2fs.conf. If

    you have edited the /etc/mke2fs.conf file installed on your system,

    you will need to merge your changes with the version from e2fsprogs

    1.41.x.



  - Create a new filesystem using the ext4dev filesystem type:

  - Create a new filesystem using the ext4dev filesystem type:





    	# mke2fs -t ext4dev /dev/hda1

    	# mke2fs -t ext4dev /dev/hda1

Documentation/filesystems/ntfs.txt

+2 −2
Original line number Original line Diff line number Diff line
@@ -40,7 +40,7 @@ Web site 
========

========





There is plenty of additional information on the linux-ntfs web site

There is plenty of additional information on the linux-ntfs web site

at http://linux-ntfs.sourceforge.net/

at http://www.linux-ntfs.org/





The web site has a lot of additional information, such as a comprehensive

The web site has a lot of additional information, such as a comprehensive

FAQ, documentation on the NTFS on-disk format, information on the Linux-NTFS

FAQ, documentation on the NTFS on-disk format, information on the Linux-NTFS
@@ -272,7 +272,7 @@ And you would know that /dev/hda2 has a size of 37768814 - 4209030 + 1 = 
For Win2k and later dynamic disks, you can for example use the ldminfo utility

For Win2k and later dynamic disks, you can for example use the ldminfo utility

which is part of the Linux LDM tools (the latest version at the time of

which is part of the Linux LDM tools (the latest version at the time of

writing is linux-ldm-0.0.8.tar.bz2).  You can download it from:

writing is linux-ldm-0.0.8.tar.bz2).  You can download it from:

	http://linux-ntfs.sourceforge.net/downloads.html

	http://www.linux-ntfs.org/

Simply extract the downloaded archive (tar xvjf linux-ldm-0.0.8.tar.bz2), go

Simply extract the downloaded archive (tar xvjf linux-ldm-0.0.8.tar.bz2), go

into it (cd linux-ldm-0.0.8) and change to the test directory (cd test).  You

into it (cd linux-ldm-0.0.8) and change to the test directory (cd test).  You

will find the precompiled (i386) ldminfo utility there.  NOTE: You will not be

will find the precompiled (i386) ldminfo utility there.  NOTE: You will not be