I followed up with Google on why DragonFly isn’t in Summer of Code this year. It is exactly as I suspected: they want to get new organizations in. DragonFly’s been doing it for 6 years, so they are picking new orgs over returning ones. This is apparently the same reason NetBSD isn’t in this year, either.
(Honestly, I can use the break.)
DragonFly wasn’t accepted for Summer of Code, which frankly I expected to have happen last year – we’ve been participating every year since 2008. However, FreeBSD and (for the first time) OpenBSD are listed as participating mentoring institutions, so you can still get your BSD/GSoC going.
Here’s a potential DragonFly and Summer of Code project: adding support for more than 63 cores to DragonFly. Matthew Dillon has already outlined how.
I put in the application for Google Summer of Code 2014, for DragonFly. Will we get in for a 7th year? I hope so!
(I still want more mentors; contact me if you’re interested.)
I already asked this question on kernel@, but I’ll repeat it here. Who is interested in mentoring for DragonFly, for Google Summer of Code 2014? The org application period is starting today, and it would be neat to do this for a seventh year in a row.
Markus Pfieffer has committed Larisa Grigore’s Google Summer of Code work, “SysV IPC in userspace”. It’s been a bit since the event finished, but it’s in DragonFly now.
Google has a post up about the 10th anniversary of Summer of Code, with next year’s version of the event getting some changes – an increase in the students allocated and in the student stipend, and more events. I’m planning to apply for DragonFly, for 2014.
Google is also doing the Code-In, for 13 to 17-year-old students, again. DragonFly participated in the first year (the only BSD to do so), but sat out last year. I’m not currently anticipating DragonFly being involved for 2013, cause of reasons. (It’s a lot of work!)
I had this to post, and managed to miss it: Daniel Flores, whose Summer of Code project was Hammer compression, posted a final report.
I know I said Summer of Code was complete for DragonFly, but Larisa Grigore published some rough benchmarks of her “SysV IPC in userland” work, plus a followup.
This will not be a surprise to anyone seeing the work being done, but: All 5 DragonFly/Summer of Code students for 2013 passed, as noted today in emails from Google. It was possibly our best year yet in terms of buckling down and just plain working.
More Summer of Code wrapups: Larisa Grigore has posted a final report on SysV IPC work, and Mihai Carabas has posted his on hardware support for vkernels.
(Mihai’s report was out several days ago and I didn’t realize it, sorry!)
Joris GIOVANNANGELI and Pawel Dziepak both have published final reports for this year’s DragonFly/Summer of Code experience. Both of them say they want to keep working on DragonFly, which is exactly the result I want. There may be more if the other students have time. A final report wasn’t required, but it is good feedback.
Related: Joris is working on Capsicum for DragonFly and published an API document describing how it has worked/will work.
Please welcome our newest committers: Joris Giovannangeli and Mihai Carabas. Joris has already updated bc(1) and dc(1) to match what OpenBSD has. You may recognize Joris’s name from his just-finished Google Summer of Code project for DragonFly, and Mihai Carabas from both this year’s and last year’s Summer of Code.
Matthew Dillon’s committed the work by Daniel Flores on Hammer 2 compression and Mihai Carabas’s vkernel hardware support – both Summer of Code projects. There’s a good amount of detail in the commit messages describing the work and what it changed; I expect more Summer of Code work to be getting committed…
Note: you’ll want to do a full update.
We’re in the last week of what has been a very good Summer of Code for DragonFly, and here’s the last reports. (We’re missing two, but this is cleanup week, so not much to report)
I know this is late; my schedule is a bit messed up. This is the penultimate week!
Almost done with this year’s GSoC. It’s been astonishingly… easy? The students are working and the problems are difficult, but there’s been very little in the way of crisis.
Only 3 more Mondays left in the student work part of Summer of Code! Unsurprisingly, it seems the students are mostly in the cleanup phase – as it should be.
I’m running a bit behind because I’ve been on the road, but here they are:
If you look at the reports from students this week, they are mostly “I had bugs and I fixed them and there’s not much to do other than test”, which is the sign of well-planned projects. Here’s the status reports:
Everyone passed their Summer of Code midterms! Not that this was a surprise; all the students have been consistently working and overcoming problems, but a 100% pass rate makes me happy.
Here’s the status reports:
Joris Giovannangeli, one of the Summer of Code students for DragonFly, posted his thoughts on credential descriptors – have a read. He is working on capsicum and DragonFly, so this is a natural thought process.
Every year, people ask “Why can’t writing documentation be part of Summer of Code?” (Not necessarily for DragonFly, but in general) Google has a “Doc Camp”, where a whole lot of documentation gets produced in sprints, and anyone can participate – not just Summer of Code students.
If this sounds interesting to you, your application has to be in by August
7th 9th. (URL and date updated)
It’s week 6, I think, and the midterms are coming up. Here’s the status reports:
I’m late for this, even though the students weren’t. Mea culpa! There’s been a lot of discussion on IRC, in EFNet #dragonflybsd, between the students and various DragonFly developers.
We’ve never had a group of student post progress this regularly. It’s great!
Week 3 is underway, and the students are starting to get into the meat of their projects:
All the Summer of Code students for DragonFly have posted their second week reports:
There’s a lot of progress for the second week, which is wonderful!
Earlier this week, Daniel Flores posted the first-week report on his Google Summer of Code project, file compression in Hammer. He mentioned that the LZ4 algorithm he is using seems to have the best performance with repeating text data, as in logfiles. I asked for numbers, and he provided them. The important data in the results is the total compression column. It shows how many 64k blocks were able to be compressed, with that type of data.
All the Summer of Code students for DragonFly have posted their first week reports:
If any of these projects are interesting to you, or if you have any tips for these students on work they are doing, please provide feedback.
Larisa Grigore posted an introduction of her Summer of Code project: Userland System V IPC in userland, and Daniel Flores wrote out his initial ideas for Hammer compression. That’s the remaining two projects introduced. If any of these interest you or you want to make suggestions, respond on the lists. Work starts on the 17th.
Pawel Dziepak has posted details on his Summer of Code project for DragonFly. He will be making it possible to checkpoint vkernels, restoring network and console state. He even has a public repository for his work set up.
Another DragonFly/Google Summer of Code project introduction is up: Mihai Carabas wrote out his project on developing hardware nested page table support for vkernels. If Mihai’s name seems familiar, it’s because he was in Summer of Code for DragonFly last year, with a successful project.
Joris GIOVANNANGELI has posted a description of his Summer of Code project for DragonFly, implementing the Capsicum kernel APIs. I expect the other students will post summaries soon, too.
Here’s the accepted projects for DragonFly and Google Summer of Code 2013:
- Block compression feature in HAMMER2, Daniel Flores Tafur, mentored by Matthew Dillon
- Capsicum kernel implementation, Joris GIOVANNANGELI, mentored by Alex Hornung
- Implement hardware nested page table support for vkernels, Mihai Carabas, mentored by Venkatesh Srinivas
- Make vkernels checkpointable, Pawel Dziepak, mentored by Samuel Greear
- Userland System V Shared Memory / Semaphore / Message Queue implementation, Grigore Larisa-Ileana, mentored by Markus Pfeiffer
Like last year, we had more excellent proposals than we could accommodate with available slots and mentors. We now enter the ‘community bonding’ period, so that students can get used to the DragonFly environment and make sure they have all the tools needed to perform work. The work itself starts on June 17th.
Good luck to everyone involved!
We’re in the picking and choosing stage of Summer of Code. I posted a note to kernel@ describing the next dates to watch for.
Now’s the time to put in your application for Summer of Code projects, if you’re a student. The application period runs until May 3rd. There’s already been some proposals on the mailing lists; now they can be put in officially.
I’ll point out the last link is from a returning GSoC student, and has a lot of detail; use that as an example if you’re thinking about your own application.
For anyone who is a student considering Google Summer of Code this year: this timeframe we’re in right now is listed by Google as time for “students discuss project ideas with mentoring organizations”. This is the perfect time to find out what the people in an organization are like, and get early feedback on your project ideas.
Chances are, if you’re submitting a proposal for an idea from an org’s project list, you’re one of a number of students all trying for the same thing. The best way to get accepted instead of any other applicant is to be the person they already know.
The DragonFly page on the Summer of Code site is set up. If you are a potential mentor that I’ve talked to before, I’ve already sent you an email with details. If you are a potential mentor I haven’t talked to, you can email me or send a request via the DragonFly page. (Google has a new ‘connections’ method for signup this year.)
If you’re an interested student, take a look at the DragonFly Projects Page. Keep in mind that your proposal does not have to be one of those ideas – new projects are always welcome, and often have the advantage of being unique instead of being one of several similar proposals. (hint, hint)
We’re accepted! The application requirements, etc. will be up on the Google Summer of Code site as soon as I can fill out the forms.
I’ve put in an application for DragonFly to be a Google Summer of Code mentoring organization for the 6th year in a row – we have mentors lined up, so we’ll know by the Friday after next. See my post on kernel@ for pretty much what I just said.
Meaning, Summer of Code for the teachers, not the students. Google apparently has a grant program for academic researchers, that runs twice a year. I didn’t know this, but I bet there’s someone who is 1: in academia and 2: needs cash money that is 3: reading this.
If DragonFly is going to participate in Google Summer of Code for 2013, we need project ideas, and lots of them, at any size. There’s an existing project page that anyone can add to, especially if you’re a student and looking to add your ideas.
It’s announced! If DragonFly is going to participate again for the sixth year in a row (wow!), we need mentor volunteers…
Google is hosting a ‘Doc Camp’, where people get together and write documentation for open source projects. There’s a page that talks about it. Last year’s inaugural event was apparently quite successful. I haven’t been to it, but I think a day just for documentation is a good idea.
If you ever wanted to read an extensive discussion about the scheduler, today’s your day. Mihai Carabas, who posted the details of a long discussion he had with Matthew Dillon about how the scheduler works. You may recall Mihai’s name from the very successful GSoC scheduler project that recently finished.
(look, a link to the new Mailman archive!)
DragonFly had a successful Google Summer of Code even this year. It marks our 5th time participating, 7th if you count Google Code-In events.
Mihai Carabas worked on adding SMT/HT awareness to the DragonFly scheduler. This project was very successful. The original goal was just to take advantage of threading with the scheduler, but the benchmarks published by Mihai show in general a 5% speedup from these scheduler changes. His work has already been committed.
Vishesh Yadav implemented an inotify interface in DragonFly. inotify is an originally Linux-based system for monitoring files and directories for changes. A specific use for this is an inotify-aware locate program, so that a list of file locations can be kept ‘live’. His code for the inotify interface should be committed to DragonFly very soon.
(This was written in part for Google to use on their Open Source Blog.)
I was on the road and missed last week’s summaries for Summer of Code, and we’re almost at the end of the session, so I’ll just link to the most recent items from Mihai Carabas (there’s a lot there!), Vishesh Yadav, and Ivan Freitas.
Mihai Carabas has posted some more results from an 8-core system showing his efforts to make the scheduler multi-threading aware. The results are generally a 5% speed gain, which I think matches previous benchmarks on machines with less processors.
I hope it’s week 8. Anyway here’s the reports from Mihai Carabas, Vishesh Yadav, and Ivan Sichmann Freitas.
At least for DragonFly, every current participant in Google Summer of Code passed the midterm evaluation. Yay!
Here’s the regular status updates for Mihai Carabas (scheduler) and Vishesh Yadav (inotify).
I don’t have the update from Ivan Sichmann Freitas yet. Here’s Ivan Sichmann Freitas.
The usual weekly updates from Mihai Carabas, Vishesh Yadav, and Ivan Sichmann Freitas. Mihai has some interesting bugs found this past week by running his code on Matt Dillon’s 48-core system.
Attention students and mentors: the Summer of Code midterms open up on July 9th. This means students fill out an evaluation, and mentors also fill out an evaluation. Don’t forget, because completed evals from mentor and student both are necessary for a project to continue being funded.
This is a report for last week’s work, so this is week 6 we are in now, and the reports are week 5’s status. So:
If you have an Intel processor with multiple cores and hyperthreading support, you can compile a new kernel and try out Mihia Carabas’s GSoC work already; he’s created a test using the OpenSSL test case to time scheduling performance vs. number of threads.
Mihai Carabas posted some benchmarks for his work with the DragonFly default scheduler and hyperthreaded CPUs. The end result, for those who don’t like number analysis, is that CPU-dependent speeds are reliably constant because tasks are being evenly scheduled across available CPUs.
(Well, CPU threads, since this is hyperthreading, but you get the idea.)
I think it’s week four, at least.
Mihai Carabas, Vishesh Yadav, and Ivan Sichmann Freitas all have their weekly status reports up for Summer of Code. Unfortunately, Loganaden Velvindron received a great job offer out of the blue, so he no longer has time for Summer of Code. (He plans to continue involvement in DragonFly, however.)
Here’s your most recent weekly round of DragonFly/Google Summer of Code updates:
Three more weekly status updates from DragonFly/GSoC students: Mihai Carabas, Vishesh Yadav, and Ivan Sichmann Freitas. That’s all for the past/first week.
Loganaden Velvindron posted a terse update on the state of his Summer of Code work for DragonFly. I’m still waiting on the other students.
Each of the 4 DragonFly participants for Summer of Code have posted an introductory email and details of their projects. Here’s direct links to their posts for your reading convenience:
(Yes, same format as my last post, but now the links are to their posts, not the sparse Google info pages.)
Google has announced their projects accepted for Summer of Code: DragonFly has 4 projects of the 1,212 funded:
(Hopefully those links are to visible pages) We had way more good proposals than available mentors/slot, unfortunately. So if you didn’t get in, think about next year, or maybe look at doing the work on your own; there’s some great ideas out there that I’d like to see happen.
DragonFly has been given 6 slots (i.e. spaces for students) by Google for this year’s Summer of Code. That’s great! We have a crop of great student proposals this year, so far, so the biggest worry at this point is how to get to them all.
Student applications for Google Summer of Code (and DragonFly) can now be submitted, until April 6th. Now’s your chance!
Here’s the page, with a convenient mentor application note at the bottom. That’s the next step, so if you were thinking of mentoring, now is the time.
The organization application for DragonFly is in for Google Summer of Code. If you are thinking of working as a mentor or as a student, please let me know soon! We will know if we’re accepted (for the 5th time!) on the 16th.
Nick Prokharau’s project for Google Summer of Code last year was “Port PUFFS from NetBSD/FreeBSD”. Sascha Wildner has now committed that to DragonFly. It’s experimental, so the normal caveats apply.
Google has announced that Summer of Code 2012 is in the works. I’ve announced that DragonFly will apply again. For that, I need to know who wants to be a student or a mentor, and what ideas people want to suggest.
It’s on, again! Not that there was any doubt. I need to collect potential mentor names before DragonFly can be involved, so you can guess what I’ll say next…
That would be a recent ATI card, though I don’t know exactly which model name. Samuel Greear has imported David Shao’s DRM work, originally for Summer of Code, last year. Most newer Radeons should work (?).
I got mine the other day, and here’s someone else’s.
DragonFly had another good year with Google’s Summer of Code program. We had 6 slots, and 5 passed projects. (Irinia, if you’re reading this – where did you go?) This is our 4th year participating in Summer of Code, with I think the highest number of passed projects to date.
Here’s all the finished projects, with links to the original descriptions:
Thanks is also due to the mentors and other that helped out, via IRC and email: Aggelos Economopoulos, Alex Hornung, Joe Talbott, Matthias Schmidt, Michael Neumann, Nathaniel Filardo, Pratyush Kshirsagar, Sascha Wildner, Thomas Nikolajsen, and Venkatesh Srinivas
You can also check the Digest’s “Google Summer of Code” category for progress reports made as the summer went on. The source code from the projects is available at the DragonFly/SOC 2011 Google Project Page. In even better news, 2 of the projects have already been partially committed to DragonFly – Brills Peng’s scheduler work, and Adam Hoka’s device mapper mirror project.
Brills Peng has written up a nice description of his scheduler work for Google Summer of Code, with details on what it does, and how to try it out. Best of all, he plans to keep working on it!
Another batch of code has arrived from Google Summer of Code student work. In this case, it’s code from Adam Hoka’s “Implementing a mirror target for device mapper” project, committed by Alex Hornung. I think there’s potentially more to come.
Google Summer of Code for 2011 just finished, and there’s already source code from it showing up in DragonFly. In this case, scheduler work, including multiple schedulers. I’ll have a more detailed report soon…
Anton Panev is working on a Google Summer of Code project for NetBSD, adding support in pkgsrc for RPM/Debian package formats. He posted a status report recently; will this come to DragonFly via pkgsrc? I don’t know!
Samuel Greear posted a progress report on his kqueue Summer of Code project. There’s code available now to try it out. It sounds grand, though I can’t identify what effects it will have for the end user.
All 6 Google Summer of Code projects for DragonFly have reached the midterm, and passed!