summerofcode2008

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
summerofcode2008 [2009/04/14 21:30] – TimKientzlesummerofcode2008 [2020/02/10 09:18] (current) – Added Gsoc category TrevorRoydhouse
Line 1: Line 1:
-The %%FreeBSD%% Project was awarded 21 slots for student project in this year's [[SummerOfCode|Summer of Code]], although we had many more worthy applications.  Final project summaries for each project may be found below.+The %%FreeBSD%% Project was awarded 21 slots for student project in this year's [[SummerOfCode|Summer of Code]], although we had many more worthy applications.  Final project summaries for each project may be found below.  More information about the program is available on [[http://code.google.com/soc/2008/|Google's Summer of Code 2008]] web site.
  
 ====== Links to Project Pages ====== ====== Links to Project Pages ======
  
-  * [[MayurShardul/VM_Algorithm_Improvement|VM Algorithm Improvement]], by MayurShardul, mentored by JeffreyRoberson +  * [[MayurShardul/VM_Algorithm_Improvement|VM Algorithm Improvement]], by MayurShardul, mentored by JeffRoberson 
-  * [[NFSv4_ACLs]], by %%EdwardTomaszNapiera%%ła, mentored by RobertWatson +  * [[NFSv4_ACLs]], by EdwardTomaszNapierala, mentored by RobertWatson 
-  * [[PortsLicenseInfrastructure|Ports license auditing infrastructure]], by AlejandroPulver, mentored by BrooksDavis+  * [[Ports/LicenseInfrastructure|Ports license auditing infrastructure]], by AlejandroPulver, mentored by BrooksDavis
   * [[Porting_FreeBSD_to_Efika_(PPC_bring_up)]], by PrzemekWitaszczyk, mentored by RafalJaworowski   * [[Porting_FreeBSD_to_Efika_(PPC_bring_up)]], by PrzemekWitaszczyk, mentored by RafalJaworowski
   * [[KonradJankowski/Collation|Multibyte collation support]], by KonradJankowski, mentored by DiomidisSpinellis   * [[KonradJankowski/Collation|Multibyte collation support]], by KonradJankowski, mentored by DiomidisSpinellis
Line 64: Line 64:
 Use of small tests. So we can cover a wide range of traffics, events and transitions predetermined separately. The development would be like a protocol, but without covering all possible events and transitions, only traffic previously determined. Instead of targeting a TCP Finite State Machine (FSM) like the implementation of TCP/IP protocols, the development will be based towards flow of packets, where traffic is composed of packets that are sent and received in a previously registered way. Use of small tests. So we can cover a wide range of traffics, events and transitions predetermined separately. The development would be like a protocol, but without covering all possible events and transitions, only traffic previously determined. Instead of targeting a TCP Finite State Machine (FSM) like the implementation of TCP/IP protocols, the development will be based towards flow of packets, where traffic is composed of packets that are sent and received in a previously registered way.
  
-Links: http://wiki.freebsd.org/VictorBilouro/TCP-IP_regression_test_suite (project wiki) http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/bilouro_tcptest/src (freebsd repository) http://code.google.com/p/tcptest/ (source code download) http://bilouro.com/tcptest (source code documentation) http://pcs.sf.net - Packet Construction Set+Links: [[VictorBilouro/TCP-IP_regression_test_suite]] (project wiki) http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/bilouro_tcptest/src (freebsd repository) http://code.google.com/p/tcptest/ (source code download) http://bilouro.com/tcptest (source code documentation) http://pcs.sf.net - Packet Construction Set
  
 ---- ----
Line 133: Line 133:
   * for last few days I'm working on implementing expansions, I'll not rest until they work   * for last few days I'm working on implementing expansions, I'll not rest until they work
   * I wasn't able to start writing manpages and create a megapatch agains HEAD, I'll do that when the algorithm is 100% correct for all the languages.   * I wasn't able to start writing manpages and create a megapatch agains HEAD, I'll do that when the algorithm is 100% correct for all the languages.
-Current informatin will be available on my wiki: http://wiki.freebsd.org/KonradJankowski/Collation+Current informatin will be available on my wiki: [[KonradJankowski/Collation]]
  
 **Ready to enter CVS:** After finishing expansion support and cleanup. **Ready to enter CVS:** After finishing expansion support and cleanup.
Line 171: Line 171:
 I was a bit late developing results because the %%SoC%% began before my exams did (I was still having classes), but now, that "damage" is partly fixed. ;-) Overall, this %%SoC%% was a really interesting learning experience. I must say that my TCP knowledge has increased a few points. :-) I was a bit late developing results because the %%SoC%% began before my exams did (I was still having classes), but now, that "damage" is partly fixed. ;-) Overall, this %%SoC%% was a really interesting learning experience. I must say that my TCP knowledge has increased a few points. :-)
  
-Andre Oppermann is my mentor. I blogged a bit about this project at http://blogs.freebsdish.org/rpaulo/ . The wiki page is at http://wiki.freebsd.org/RuiPaulo/TCPAnomaly .+Andre Oppermann is my mentor. I blogged a bit about this project at http://planet.freebsd.org/rpaulo/ . The wiki page is at [[RuiPaulo/TCPAnomaly]]
  
 **Ready to enter CVS:** No. **Ready to enter CVS:** No.
Line 207: Line 207:
 I intend to do further testing and benchmarking to find the best default values to use for vfs.ufs.dirhash_reclaimage (the number of seconds a dirhash can sit unused before the dirhash low memeory event handler will unconditionally delete it) and the minimum percentage of memory that will be freed upon vm_lowmem events even if there are not enough hashes older than dirhash_reclaimage (currently this is hard coded to 10%). I would also like to add some code to choose a reasonable new default vfs.ufs.dirhash_maxmem value based upon the amount of memory in the system, set automatically at boot time and tunable via sysctl. Once these tweaks have been made I plan to ask for testing from more users to shake out any bugs or potential workloads where the new code may hurt overall performance. I intend to do further testing and benchmarking to find the best default values to use for vfs.ufs.dirhash_reclaimage (the number of seconds a dirhash can sit unused before the dirhash low memeory event handler will unconditionally delete it) and the minimum percentage of memory that will be freed upon vm_lowmem events even if there are not enough hashes older than dirhash_reclaimage (currently this is hard coded to 10%). I would also like to add some code to choose a reasonable new default vfs.ufs.dirhash_maxmem value based upon the amount of memory in the system, set automatically at boot time and tunable via sysctl. Once these tweaks have been made I plan to ask for testing from more users to shake out any bugs or potential workloads where the new code may hurt overall performance.
  
-Current details about status are on the wiki here: http://wiki.freebsd.org/DirhashDynamicMemory+Current details about status are on the wiki here: DirhashDynamicMemory
  
 ---- ----
Line 290: Line 290:
 The license database (a list of them and their properties) was going to be mirrored from FOSSology: a tool to analyze software licenses. We're working on getting FOSSology to automatically classify ports (I've sent suggestions and patches to the developers, who accepted them and provided very good support). So for the moment it's not usable (at least licenses/properties are defined manually, and each port is marked manually to indicate its license). The license database (a list of them and their properties) was going to be mirrored from FOSSology: a tool to analyze software licenses. We're working on getting FOSSology to automatically classify ports (I've sent suggestions and patches to the developers, who accepted them and provided very good support). So for the moment it's not usable (at least licenses/properties are defined manually, and each port is marked manually to indicate its license).
  
-I'll continue working on the FOSSology's port, and on the missing features such as multiple licenses support (AND, OR, etc). For more information see the wiki page: [[PortsLicenseInfrastructure|Ports license auditing infrastructure]]+I'll continue working on the FOSSology's port, and on the missing features such as multiple licenses support (AND, OR, etc). For more information see the wiki page: [[Ports/LicenseInfrastructure|Ports license auditing infrastructure]]
  
 **Ready to enter CVS**: not yet **Ready to enter CVS**: not yet
Line 314: Line 314:
 options added. options added.
  
-Details and usage examples are on my blog: http://blogs.freebsdish.org/gleb/+Details and usage examples are on my blog: http://planet.freebsd.org/gleb/
  
 **Ready to enter CVS:** Not yet, diff is submitted to freebsd-net@ for public review. **Ready to enter CVS:** Not yet, diff is submitted to freebsd-net@ for public review.
Line 335: Line 335:
 As for now, half of the project is realized. After solving a few difficult As for now, half of the project is realized. After solving a few difficult
 problems at the basic level (binary interface issues with entry point to the problems at the basic level (binary interface issues with entry point to the
-SmartFirmware on the device), the boot procedure reaches the device+%%SmartFirmware%% on the device), the boot procedure reaches the device
 drivers initialization stage, and hits the PIC driver init. At this point, the driver skeleton is constructed and is called. The driver uses ofwbus bus driver which drivers initialization stage, and hits the PIC driver init. At this point, the driver skeleton is constructed and is called. The driver uses ofwbus bus driver which
 intermediates between the openfirmware and the %%FreeBSD%% newbus devices hierarchy. After completing the PIC driver, I'll be in the position to write the remaining drivers for peripherals integrated on the MPC5200B chip using the newbus architecture. intermediates between the openfirmware and the %%FreeBSD%% newbus devices hierarchy. After completing the PIC driver, I'll be in the position to write the remaining drivers for peripherals integrated on the MPC5200B chip using the newbus architecture.
Line 342: Line 342:
 date in order to bring at least the interrupt controller driver to operation.. date in order to bring at least the interrupt controller driver to operation..
  
-More info available at project's wiki : +More info available at project's wiki: PrzemekWitaszczyk and at my %%GSoC%% 2008 blog: http://bitbay.blogspot.com/
-http://wiki.freebsd.org/PrzemekWitaszczyk +
-and at my %%GSoC%% 2008 blog: http://bitbay.blogspot.com/+
  
 **Ready to enter SVN:** not yet, at least PIC driver required. **Ready to enter SVN:** not yet, at least PIC driver required.
Line 363: Line 361:
  
 More information can be found here: More information can be found here:
-http://wiki.freebsd.org/DiegoGiagio/Audit_Firewall_Events_from_Kernel+[[DiegoGiagio/Audit_Firewall_Events_from_Kernel]]
  
 **Ready to enter SVN:** Not determined yet, perhaps parts of it. **Ready to enter SVN:** Not determined yet, perhaps parts of it.
Line 370: Line 368:
 **Project**: Create a tiny operating system from %%FreeBSD%% **Project**: Create a tiny operating system from %%FreeBSD%%
  
-**Student**: James Harrison+**Student**: JamesHarrison
  
-**Mentor**: Warner Losh (bsdimp@)+**Mentor**: WarnerLosh
  
 **Summary**: **Summary**:
Line 383: Line 381:
  
 **Ready to enter SVN:** Not yet, though when the Makefile is complete it would be good to offer it up for inclusion in base. **Ready to enter SVN:** Not yet, though when the Makefile is complete it would be good to offer it up for inclusion in base.
 +
 +----
 +
 +{{tag>Historical Gsoc}}
  
  • summerofcode2008.1239744642.txt.gz
  • Last modified: 2009/04/14 21:30
  • by TimKientzle