Muli Ben-Yehuda's Journal
[Most Recent Entries]
[Calendar View]
[Friends]
Below are the 20 most recent journal entries recorded in
Muli Ben-Yehuda's LiveJournal:
[ << Previous 20 ]
| Tuesday, April 7th, 2009 | | 4:01 pm |
SYSTOR 2009 Call for Participation
CALL FOR PARTICIPATION
SYSTOR 2009---The Israeli Experimental Systems Conference
http://www.haifa.il.ibm.com/conferences/systor2009/
4-6 May 2009
Haifa, Israel
Registration deadline: May 2nd
SYSTOR 2009, the Israeli Experimental Systems Conference, will be held
at IBM Haifa Labs, in Haifa, Israel. The conference program will run
over three days, combining the forefront of academic systems research
with real-world systems developed in industry. The goal of the
conference is to promote systems research and to foster stronger ties
between the Israeli and worldwide systems research communities and
industry. Conference proceedings will be published by ACM in the ACM
Digital Library.
There is a limited number of seats available on a
first-come-first-served basis upon registration at
http://www.haifa.ibm.com/conferences/systor2009/registration.shtml
(registration is free of charge). Lunch and refreshments will be
served on all three days courtesy of IBM Haifa Labs.
The first day of the conference will feature sessions on distributed
systems, concurrency, and power management. Marc Snir, University of
Illinois at Urbana Champaign, will give a keynote talk, and in the
afternoon a student poster session with sweet refreshments will be
held.
The second day will begin with the keynote "Towards Invisible Storage"
by Alain Azagury, Director, XIV Business Executive, IBM, and an
invited talk on "The Next Generation Data Center" by Michael Kagan,
Mellanox CTO. After the morning talks, there will be paper sessions
focusing on data de-duplication and storage issues. The day will end
with an optional social event in Caesarea.
The third day will conclude the conference with paper sessions on
virtualization and system optimizations, and a panel of well-known
systems researchers who will debate "What is Systems Research about
and is it Relevant?" The full program for all three days is available
on the conference website.
We look forward to seeing you at SYSTOR 2009!
SYSTOR Advisory Committee
* Marc Auslander, IBM
* Ken Birman, Cornell
* Danny Dolev, HUJI
* Julian Satran, IBM
* Marc Snir, UIUC
* Willy Zwaenepoel, EPFL
Program Chairs
* Michael Factor, IBM
* Dror Feitelson, HUJI
General Chair
* Miriam Allalouf, IBM
Publicity Chair
* Muli Ben Yehuda, IBM
Publication Chair
* Gregory Chockler, IBM
| | Sunday, April 5th, 2009 | | 12:11 am |
miscellany
I want to update this thing more often, but there's so much going on, the days filled with action and counter-action, that before I know it it's past midnight, and I have to wake up at 5 AM for a workout, and updating the blog is left on the TODO list for yet another day. Like, today. So, content? I've been a manager for a month and change now, managing the virtualization and systems architecture group at the lab. It's an interesting challenge (which is why I agreed to do it), often frustrating, occasionally exhilarating. To my surprise, the part I like most is dealing with human beings in their myriad forms. To my non-surprise, the part I like least is the bureaucracy, but I figured I'd wait a couple more months before I start tilting at wind-mills. I still write code (well, debug code, mostly) and conduct research, but it's no longer the most important part of my day. On the research front, we had two papers accepted to ICAC 2009 (one full paper and one short paper/poster), both in the general area of treating virtual machines as black boxes and inferring useful things about them---performance bottlenecks and boot-time--via statistical analysis of their inputs and outputs. Another paper, on the DMA mapping problem in direct assignment, was not accepted to USENIX ATC to my disappointment, and we are now revising it while looking for a new home. I am continuing to work out twice a week with a private trainer who is seriously kicking my butt. It's rare when I don't finish a workout on the brink of exhaustion, drenched in sweat. I *love* it. Twice a week is no longer enough---I crave the endorphin rushes and sore muscles---so I've also re-started going for long walks, and hitting the punching bag in the back-yard like I really mean it. The kilograms are coming off, too, an added bonus. Last but not least, SYSTOR 2009 is coming up next month, with a great program combining academic research and real-world systems. See y'all there! Current Music: Midsummer Eve on TV | | Wednesday, January 28th, 2009 | | 5:50 am |
It's 5:40 AM. I am is sitting in an empty room full of half-assembled furniture, waiting for the personal trainer to arrive and whip my ass into shape. | | Tuesday, December 23rd, 2008 | | 11:21 pm |
There will be a half-day workshop at the Technion's EE department on Thursday afternoon on "Technology Transfer - from Academy to Industry" which looks mildly interesting. I am on nominally on vacation this week and flying to Italy that night, but perhaps I'll go anyway. Anyone else planning to go? | | Wednesday, December 10th, 2008 | | 11:17 am |
Scalable I/O paper online
Our new paper is online: "Scalable I/O---A
Well-Architected Way to Do Scalable, Secure and Virtualized I/O",
by Julian Satran, Leah Shalev, Muli Ben-Yehuda, and Zorik
Machulsky. This is an overview paper showcasing the main ideas
underlying a system we've been working on on and off since 2004. It's
not as detailed as I would've liked due to the space constraints, but
hopefully it will be followed by more detailed papers. The
slides
I'll be presenting later today at WIOV '08 are also available
and go into a bit more details in areas.
Today in both virtualized and non-virtualized systems the entire I/O
functionality is based on device drivers. They are central to any
system structure; both anecdotal and informed evidence indicates
device drivers as a major source of trouble in the classical OS and a
source of scaling and performance issues in virtual I/O, due to
"trusted intermediary" required for the shared I/O. We propose an
architecture which virtualizes the entire I/O subsystem rather than
each I/O device, and provides device-independent I/O at higher level
of abstraction than the traditional I/O interfaces. In our suggested
architecture the system robustness is increased by isolating drivers;
efficient and scalable virtualization becomes possible by a complete
separation of the I/O and compute function and introducing a
protection model that does not require a trusted intermediary for
I/O.
| | Monday, November 24th, 2008 | | 8:34 pm |
new IOMMU paper available
New online for your perusing pleasure: "Direct
Device Assignment for Untrusted Fully-Virtualized Virtual
Machines", by Ben-Ami Yassour, Muli Ben-Yehuda and Orit Wasserman,
IBM Research Report H-0263.
This is a short paper describing and evaluating our work earlier this
year on direct device assignment in KVM, using Intel's VT-d IOMMU. Not
much new here if you've read our other IOMMU papers, but it does make
two contributions. First, it's the best (and only) available
description (IMHO) of KVM's direct device assignment code, and second
it's yet another data point on the relative performance of device
emulation vs. virtual I/O drivers vs. direct device assignment. As
always, comments appreciated. The abstract follows.
The I/O interfaces between a host platform and a guest virtual machine
take one of three forms: either the hypervisor provides the guest with
emulation of hardware devices, or the hypervisor provides virtual I/O
drivers, or the hypervisor assigns a selected subset of the host's
real I/O devices directly to the guest. Each method has advantages and
disadvantages, but letting VMs access devices directly has a number of
particularly interesting benefits, such as not requiring any guest VM
changes and in theory providing near-native performance.
In an effort to quantify the benefits of direct device access, we have
implemented direct device assignment for untrusted, fully-virtualized
virtual machines in the Linux/KVM environment using Intel's VT-d
IOMMU. Our implementation required no guest OS changes and---unlike
alternative I/O virtualization approaches---provided near native I/O
performance. In particular, a quantitative comparison of network
performance on a 1GbE network shows that with large-enough messages
direct device access throughput is statistically indistinguishable
from native, albeit with CPU utilization that is slightly higher.
| | Wednesday, October 22nd, 2008 | | 11:52 am |
notes for Sunday Oct 20 through Tuesday Oct 22nd
This is not serious, I'm supposed to remember what I was doing three days ago? I can barely remember what I had for breakfast this morning. I started walking again in the mornings. Today I was up before the crack of dawn for a brisk walk on the sea shore, and when I got back home, I even had enough energy left for a few rounds with the boxing bag. Finished reading Haruki Murakami, and now re-reading Living the Martial Way. It's a funny little book, so earnest it's hard to take it seriously, but with nuggets of wisdom nonetheless. | | Sunday, October 19th, 2008 | | 9:27 am |
| | 9:24 am |
notes for Thursday Oct 16 through Saturday Oct 18
Thursday: just another day at work . In the afternoon, went to meet an amazing carpenter (US: cabinet maker). Spent three hours going over the plans in minute detail, making lots of changes, and then he told us how much it was going to cost. Staggered to Noga's cauldron for a late dinner. Friday: BBQ with old friends at Ira's. Once upon a time it would've been all Linux hacking, all the time, but now business and what the kids are doing is that much more interesting. Progress, of a sort. Saturday: a day of rest and recuperation. In the evening off to Mika's 1-year old birthday party. I still remember the sense of accomplishment we felt at Yael's 1-year old birthday party, that we actually managed to raise her and she is fine. Resumed reading Haruki Murakmi's What I Talk About When I Talk About Running. | | Thursday, October 16th, 2008 | | 11:36 am |
notes for Wednesday Oct 15
A day of odds and ends. The WIOV schedule should be going up today or tomorrow. Continued looking into the feasibility of a new project which will require coordination with an inordinate amount of people. Worked on a bunch of new patent disclosures. Hacked a bit on a new idea for IOTLB design until the serial port server stopped giving me love, and then went into paper reading mode. | | Wednesday, October 15th, 2008 | | 11:11 am |
| | 11:04 am |
notes for Tuesday Oct 14
Lunch with the Tel-Aviv, business oriented, brunch of the family in their nice new house. In the evening didn't feel like doing much of anything; ended up de-cluttering my publications page. | | Tuesday, October 14th, 2008 | | 9:45 am |
notes for Monday Oct 13
More work on the nap and vnic papers in the morning, making progress toward their respective deadlines. In the evening BBQ---fillet mignon and a good wine---with my folks in our garden. | | Sunday, October 12th, 2008 | | 9:41 pm |
notes for Sunday Oct 12
Woke up bleary eyed, but settled into a productive day at the office debugging by proxy and reviewing a couple of draft papers (vnic and nap). In the evening got some work done on the secret project, too. | | 1:38 pm |
| | 8:51 am |
notes for Satuday Oct 11th
Planned, prepared for and executed Yael's 2-year birthday. Splendid success, including several tipsy family members. Pictures to come. Cleaned up afterwards and eventually crashed. Woke back up at 2:30 AM and tried to convince Yael to go back to sleep until 4 AM. Re-crashed. | | Saturday, October 11th, 2008 | | 8:55 am |
| | Tuesday, August 26th, 2008 | | 6:43 pm |
I'm a-twitter
I was working from home today and didn't have anyone to talk to. So I finally bit the bullet and figured, why talk to *someone*, when I can talk to *everyone*? Hence, muliby on twitter. Leave a comment if you're on twitter. | | Thursday, August 7th, 2008 | | 5:06 am |
WIOV '08 CFP
It is my great pleasure to invite all of you to submit papers and participate in the First Workshop on I/O Virtualization (WIOV '08), to be held in conjunction with OSDI '08.
First Workshop on I/O Virtualization (WIOV '08)
December 10–11, 2008, San Diego, CA, USA
http://www.usenix.org/wiov08
WIOV '08 will be held in conjunction with the 8th USENIX Symposium on Operating Systems Design and Implementation (OSDI '08), December 8–10, 2008.
Overview
Over the past decade, the use of virtualization technology has grown rapidly. Moreover, it is being used in a variety of places, ranging from the data center to the desktop. Although this has spurred great advances in processor and memory virtualization in commodity hardware and virtualization software, I/O virtualization has received far less attention. However, both personal computers and servers may perform significant amounts of I/O. For example, efficient virtualization of graphics hardware has presented significant challenges on the desktop and efficient virtualization of network interfaces has limited server consolidation in the data center.
This workshop is meant to provide a forum to discuss challenges of I/O virtualization that span the virtual machine monitor, guest operating system, processor, memory subsystem, and I/O subsystem. In that spirit, we welcome papers that describe new challenges in I/O virtualization and papers that describe novel approaches to solving known problems in I/O virtualization. The final program will consist of both reviewed submissions and invited talks. The invited talks will focus on open problems in I/O virtualization and will be accessible to a broad audience.
Topics of interest include but are not limited to:
* Hardware support for I/O virtualization
* Novel I/O device architectures for virtualization
* Novel software approaches to I/O virtualization
* Software methods for I/O device emulation
* Para-virtualized I/O device driver design for virtualization
* Virtual machine monitors I/O subsystems
Important Dates
Submissions due: September 15, 2008
Notification to authors: October 3, 2008
Final files due: November 3, 2008
Workshop Organizers
Program Co-Chairs
Muli Ben-Yehuda, IBM Haifa Research Lab
Alan L. Cox, Rice University
Scott Rixner, Rice University
Program Committee
Eyal de Lara, University of Toronto
Jun Nakajima, Intel
Renato Santos, HP Labs
Karsten Schwan, Georgia Institute of Technology
Pratap Subrahmanyam, VMware
Leendert van Doorn, AMD
Andrew Warfield, University of British Columbia
Submission Guidelines
Please submit an extended abstract in PDF format through the workshop submission web form, which will be available at http://www.usenix.org/wiov08 soon. The extended abstract should be no more than 4 double-column pages using 10-point type on 12-point leading ("single-spaced"). Figures and references are not included in this 4-page limit.
| | Thursday, June 26th, 2008 | | 5:28 pm |
recent happenings and MMCS 2008 position statement
I'm in lovely Boston this week. Originally I was supposed to attend the Xen Summit North America 2008, MMCS 2008, and USENIX 2008, but I ended up missing the Xen Summit completely and making a just-in-time appearance at MMCS, due to some trouble at home. Thankfully everything is fine now. At the Xen Summit my colleague Todd DeShane presented our preliminary results of a quantitative comparison of Xen and KVM. I'm sorry I missed the summit, by all accounts I heard it was a pretty fun event. At USENIX, I presented a poster on our SCIMITAR work which introduces the notion of "virtual memory for I/O devices". It got generally positive feedback, including a few "wow, that's pretty cool" comments. I kept wishing our prototype was at a stage where we could finally have some results, but as I told those who asked, if we had had any results, I would've been presenting a paper, not a poster... At MMCS, I participated in a panel on "Platform Management---Coordination or Not?", moderated by Intel's Milan Milenkovic. Platform management is a subject that comes up fairly often in my day-to-day work, so it was fun spending some time thinking about it and trying to come up with an appropriate position statement for the panel. The way I see it, the primary function of a panelist is to encourage the audience to think, and the easiest way to do that is to be a bit controversial. A panel where everyone---both panelists and audience---agree on everything, is a dull affair. Here is my MMCS 2008 panel position statement---paraphrased, not transcribed! For context, you probably want to read the panel description first. "Hello everyone, Thank you for inviting me to participate in the panel. When thinking about the questions Milan raised with regards to platform management, I had a bit of a problem coming up with a suitable position statement. As it happens, I either wear or used to wear many different hats. I used to work on real applications. I currently work on operating systems and hypervisors, and occasionally I dabble in computer architecture. I wondered, what kind of insight could I get from each of these perspectives? From the application writer's perspective, there are three different classes of application writers: those who do not care about the platform at all, those who think they know everything best but actually don't, since they only have localized knowledge, and those that really do know everything best. From the operating systems developer perspective, you don't get too many kernel developers who don't care about the platform, so we can leave those out. That leaves two classes: those who think they know best, but are wrong since again they only have localized knowledge (think virtual machines), and those who really do know best. From the hypervisor's developer perspective, well, really, hypervisors are just a new name for operating systems! From the computer architecture folks perspective, well, they just know everything best. Having said that, they have a whole lot of legacy stuff to support which severely constrains what they can and want to do. Now, having shared with you all of these perspectives, let me share something else: none of it actually helped me come up with a good answer to the question's Milan raised. So I tried a different approach. I assume most of you are familiar with the end-to-end argument in system design, which is usually applied to networking. Well, what does the end-to-end argument tell us about platform management? As far as I can apply it, it tells us that we should let each layer do what it knows how to do best. Not a very satisfying answer. Well, let's try a different approach then. Programming language folks like to say that programming languages should make "the simple things easy, and the hard things possible". And here I think we may have actually hit on something. How does this apply to platform management? The way I interpret it, it means two things. First, that each layer in the system should make sensible decisions on its own. Second---more importantly, and hopefully somewhat controversially---that each layer should provide a "chicken switch". What's a chicken switch? It's a term you sometimes hear in hardware design. It means that when you have all these new functionality in your design, which is not as well tested (or thought out...) as the old, reliable stuff, you usually enable it (it's new and shiny after all), but you also provide a way of "shouting chicken". A way of disabling the new stuff and going back to the old, proven way of doing things. By analogy, I claim that the most important feature a platform component can have when it comes to management, is a way for the layer above or below it to tell it to "do nothing, and get out of the way". Thanks you." |
[ << Previous 20 ]
|
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
mulix's journal