From fca59bea770346cf1c1f9b0e00cb48a61b44a8f3 Mon Sep 17 00:00:00 2001
From: Harald Welte <laforge@gnumonks.org>
Date: Sun, 25 Oct 2015 21:00:20 +0100
Subject: import of old now defunct presentation slides svn repo

---
 .../OLS2005/mochel/mochel-abstract.tex             | 41 ++++++++++++++++++++++
 1 file changed, 41 insertions(+)
 create mode 100644 2005/flow-accounting-ols2005/OLS2005/mochel/mochel-abstract.tex

(limited to '2005/flow-accounting-ols2005/OLS2005/mochel/mochel-abstract.tex')

diff --git a/2005/flow-accounting-ols2005/OLS2005/mochel/mochel-abstract.tex b/2005/flow-accounting-ols2005/OLS2005/mochel/mochel-abstract.tex
new file mode 100644
index 0000000..7b6cdcc
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/mochel/mochel-abstract.tex
@@ -0,0 +1,41 @@
+
+%     Registration                     The sysfs Filesystem                   
+%  [2]Register/Submit Patrick Mochel (mochel@digitalimplant.org)              
+
+sysfs is considered by some to be one of the most       
+important and useful features that was integrated into  
+the 2.6 kernel. It has definitely been one of the most  
+talked about, most used, and most visible features. By  
+providing a window into kernel objects, their           
+attributes, and the relationships between them, a lot   
+of opportunities arise:
+\begin{enumerate}  
+\item to cleanup existing code that 
+has traditionally used proc,  
+\item to easily port code     
+that has traditionally used procfs to export object     
+attributes, and 
+\item to integrate new subsystems with     
+configurable and exportable attributes.                 
+\end{enumerate}
+
+While sysfs has been a great benefit for a large amount 
+code in the kernel, it's far from perfect. This talk    
+will discuss those imperfections, including but not     
+limited to, the places and situations where it's        
+cumbersome or inappropriate to use sysfs; how sysfs     
+suffers from some of the same problems as procfs and    
+sysctl by making it easy to duplicate code and          
+propagate bugs; and what the performance impact of      
+using sysfs is.                                         
+
+It won't be an unmitigated tomato-throwing session,     
+though. The purpose of identifying and characterizing   
+the problems is simply the first step in making it      
+better. Current developments and plans for the near     
+future to fix or alleviate the problems will be         
+described. The pundits will be placated and the critics 
+pacified in the next few steps towards total            
+domination.                                             
+
+
-- 
cgit v1.2.3

