| 
									
										
										
										
											2008-04-30 00:54:32 -07:00
										 |  |  | What:		/sys/class/bdi/<bdi>/ | 
					
						
							|  |  |  | Date:		January 2008 | 
					
						
							|  |  |  | Contact:	Peter Zijlstra <a.p.zijlstra@chello.nl> | 
					
						
							|  |  |  | Description: | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-04-30 00:54:36 -07:00
										 |  |  | Provide a place in sysfs for the backing_dev_info object.  This allows | 
					
						
							|  |  |  | setting and retrieving various BDI specific variables. | 
					
						
							| 
									
										
										
										
											2008-04-30 00:54:32 -07:00
										 |  |  | 
 | 
					
						
							|  |  |  | The <bdi> identifier can be either of the following: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | MAJOR:MINOR | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	Device number for block devices, or value of st_dev on | 
					
						
							|  |  |  | 	non-block filesystems which provide their own BDI, such as NFS | 
					
						
							|  |  |  | 	and FUSE. | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-05-23 13:04:19 -07:00
										 |  |  | MAJOR:MINOR-fuseblk | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	Value of st_dev on fuseblk filesystems. | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-04-30 00:54:32 -07:00
										 |  |  | default | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	The default backing dev, used for non-block device backed | 
					
						
							|  |  |  | 	filesystems which do not provide their own BDI. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | Files under /sys/class/bdi/<bdi>/ | 
					
						
							|  |  |  | --------------------------------- | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | read_ahead_kb (read-write) | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	Size of the read-ahead window in kilobytes | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-04-30 00:54:35 -07:00
										 |  |  | min_ratio (read-write) | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-04-30 00:54:36 -07:00
										 |  |  | 	Under normal circumstances each device is given a part of the | 
					
						
							|  |  |  | 	total write-back cache that relates to its current average | 
					
						
							|  |  |  | 	writeout speed in relation to the other devices. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	The 'min_ratio' parameter allows assigning a minimum | 
					
						
							|  |  |  | 	percentage of the write-back cache to a particular device. | 
					
						
							|  |  |  | 	For example, this is useful for providing a minimum QoS. | 
					
						
							| 
									
										
										
										
											2008-04-30 00:54:36 -07:00
										 |  |  | 
 | 
					
						
							|  |  |  | max_ratio (read-write) | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-04-30 00:54:36 -07:00
										 |  |  | 	Allows limiting a particular device to use not more than the | 
					
						
							|  |  |  | 	given percentage of the write-back cache.  This is useful in | 
					
						
							|  |  |  | 	situations where we want to avoid one device taking all or | 
					
						
							|  |  |  | 	most of the write-back cache.  For example in case of an NFS | 
					
						
							|  |  |  | 	mount that is prone to get stuck, or a FUSE mount which cannot | 
					
						
							|  |  |  | 	be trusted to play fair. |