https://www.nsnam.org/mediawiki/index.php?title=Chat-20080513&feed=atom&action=historyChat-20080513 - Revision history2024-03-29T12:41:27ZRevision history for this page on the wikiMediaWiki 1.24.1https://www.nsnam.org/mediawiki/index.php?title=Chat-20080513&diff=1593&oldid=prevTjkopena: Semi-regular, quasi-official, always entertaining IRC chats!2008-05-14T04:16:36Z<p>Semi-regular, quasi-official, always entertaining IRC chats!</p>
<p><b>New page</b></p><div>This is the archive for the IRC chat on 2008/05/13. Full transcript is below, notes follow.<br />
<br />
Participating: Florian, Hagen, Joe, Mathieu, Tom<br />
<br />
Major discussion points:<br />
<br />
* Liu has been updating the Wiki w/ Quagga notes<br />
** http://www.nsnam.org/wiki/index.php/Real_World_Application_Integration<br />
* Hagen has been working through some parallelizations basics, passing packets through sockets<br />
** Some discussion about synchronizing w/ Craig's emulation work<br />
* ns-3 demo proposal was submitted to SIGCOMM by Tom<br />
* Joe posted some basic draft code outlining the statistics framework<br />
<br />
== Transcript ==<br />
<pre><br />
* Now talking on #ns-3<br />
* Topic for #ns-3 is: gsoc: send questions to ns-developers (http://mailman.isi.edu/mailman/listinfo/ns-developers) if no one answers here<br />
* Topic for #ns-3 set by mathieu_ at Wed Mar 26 12:09:23 2008<br />
* tomh (i=824c2013@gateway/web/ajax/mibbit.com/x-7f5a787b86ea1c6b) has joined #ns-3<br />
<tjkopena> hi all<br />
<tomh> hi joe<br />
<tjkopena> hi tom; george mentioned that he wanted to stop by but is at DARPA today and can't join us (not that we had really discussed an organized chat last week)<br />
<tomh> yes, who else besides hagen is here for the gsoc chat?<br />
<tjkopena> all three are logged in, but I don't know if they're actually here<br />
<lacage> morning<br />
<tjkopena> hi lacage<br />
<hgntmp> as I know fw is finish his master theses these days, not sure if he will join us<br />
<hgntmp> good morning to everyone!<br />
<tjkopena> hi hagen<br />
<tomh> good morning<br />
<tomh> I don't know whether LJ__ is joining, but I can give a brief update<br />
<tomh> LJ__ has been developing his plan on the wiki: http://www.nsnam.org/wiki/index.php/Real_World_Application_Integration<br />
<tomh> Mathieu suggested on friday for him to get started by looking at how to support netlink sockets via the process API<br />
<tomh> that is independent of working on the regular socket api which is in flux<br />
<tomh> hgntmp, do you have a plan posted like LJ__ has done (on the wiki)?<br />
<tjkopena> LJ__'s wiki page looks good<br />
<hgntmp> btw: i am _familar_ with netlink sockets for linux (I used this as a transport mechanism some days ago)<br />
<tomh> ok, great-- will let him know<br />
<hgntmp> but as already said: netlink is one of the biggest protocols in the stack - not that easy<br />
<hgntmp> right<br />
<tomh> probably we will support, initially, the pieces needed to modify the kernel forwarding table<br />
<hgntmp> recently I looked in the olsrd implementation, they use nowadays netlinks socket for linux to manipulate them<br />
<hgntmp> (maybe a smooth introduction from userspace side)<br />
<fw_> i'm here.<br />
<hgntmp> moin<br />
<fw_> i sent mail to ns-developers that has the current state of the nsc work<br />
<fw_> i suspect that the mail is pending in the moderation queue, it will hopefull hit the list later today<br />
<hgntmp> got it<br />
<lacage> tomh, hgntmp yes, the goal is to start with only the pieces we need for zebra and these should be relatively minimal.<br />
<tomh> it did hit the moderation queue (I have whitelisted your email for the future)<br />
<lacage> hgn, so, what is the status of your work on the parallel stuff ?<br />
<tjkopena> hgntmp, have you & george been able to hookup & chat specifics?<br />
<hgntmp> really similar to the stuff i wrote to you<br />
<hgntmp> currently i stopped because I need additional information how I can convert this packet class<br />
<hgntmp> the current status:<br />
<hgntmp> i start two ns3 processes and both create a socket, one open, bind, listen and accept()<br />
<lacage> hgntmp, if you have specific questions for me, it would be more helpful to send them to the ML if you can<br />
<lacage> i.e., I am about to answer your email but it would be nice if others could see what you are up to.<br />
<hgntmp> the other one connect with the server socket<br />
<hgntmp> lacage: ok<br />
<hgntmp> afterwards I serialize the packet, get a Buffer instance, PeekData() and write() to the socket<br />
<hgntmp> the client, on the other side, read() the data, build a Buffer and afterwards a Packet instance<br />
<lacage> out of curiosity, why are you actually marshalling the packets through a socket ? do you want your parallel implementation to work on distributed machines rather than a single multicore machine ?<br />
<lacage> (for the latter, you would just need some careful locking, obviously)<br />
<hgntmp> lacage: it was the suggestion from george<br />
<lacage> ah, ok.<br />
<hgntmp> I mean it is still ok, the implementation via shared mem and semaphores (or whatever synchronization is used) could be implemented afterwards<br />
<hgntmp> there are some other fundamental challenges in the area of space parallel appraoch<br />
<hgntmp> especially for wireless (calculation interferences et cetera) <br />
<hgntmp> but I send my proposal to george and we will discuss these challenges in the next couple of days (after the trip)<br />
<lacage> cool<br />
<lacage> tjkopena, I see that you have started on the ns-3-stat branch. are you going to work on that in the next few days ?<br />
<tjkopena> yes<br />
<tjkopena> so there's an ok sketch in there<br />
<tjkopena> I am going to email vincent & the list later today<br />
<tjkopena> this evening I'm going to clean it up a bit, add another simple example (means) and demo hooking to a trace<br />
<tjkopena> hopefully I can get vincent involved & work on it together<br />
<tjkopena> I only need a couple basic things for now, so hopefully he can pick up on some of the more interesting statistics<br />
<tjkopena> I just 1) needed some of this right now and 2) wanted to make sure it was fairly general, and not tied into specific networking metrics<br />
<lacage> tjkopena, ok.<br />
<tjkopena> if you have comments on that branch I'd be happy to hear them<br />
<lacage> fw_, answered you<br />
<fw_> lacage: thanks, will read it asap<br />
<lacage> tjkopena, I will try to look at it carefully today<br />
<tomh> (reposting-- maybe I missed the response) hgntmp, do you have any plans posted like LJ__ has done (on the wiki)?<br />
<lacage> fw_, btw, were you able to catch up with sam ?<br />
<lacage> fw_, I understand that 8 in the morning is too early for a googler :)<br />
<tjkopena> lacage, sounds good; there are some design notes in docs/ as well<br />
<hgntmp> tomh: of course - I will do today - I swear! ;)<br />
<lacage> tjkopena, yeah, I saw that<br />
<lacage> tjkopena, did you have comments on my stats email from last week ?<br />
<tjkopena> yes, I thought it was a great writeup<br />
<tjkopena> not too sure on the specifics, but the motivations & goals were good, along with the references<br />
<tjkopena> I was going to crib most of it when I turn the design notes into a larger writeup<br />
<lacage> tjkopena, ok. looks like you are going to write the ns-3-stats paper :)<br />
<lacage> tjkopena, btw, did you submit a sigcomm poster ?<br />
<tjkopena> I did not in the end<br />
<tjkopena> tomh, sorry I did not get back to your email about that<br />
<lacage> tjkopena, ok. tom did submit a demo/poster proposal.<br />
<tomh> hgntmp, once your work starts to get posted, I've asked Craig Dowell to track it as well, since he is working on real-time scheduler and emulation, and is working some multicore issues there too<br />
<lacage> tomh, I replied your last email about sockets<br />
<tomh> it would be nice to harmonize craig's emulation work with your work<br />
<tjkopena> lacage, I saw that. I may still come out (have to determine that yet), in which case I'd be happy to help w/ the demo & could bring machines (tablets), etc<br />
<tomh> tjkopena, yes I submitted a demo proposal-- did you?<br />
<tomh> I'll send a copy later<br />
<tjkopena> no<br />
<lacage> tjkopena, ok. sounds great.<br />
<tjkopena> but am still thinking about coming out for it<br />
<tjkopena> also, tom (I mentioned this to lacage earlier), I'm coming out to Seattle just before the 4th of July and would be interested in getting together if people have time<br />
<tjkopena> I'm buying air tickets to night & will email everyone<br />
<tomh> great, it is a nice time around here to visit<br />
<lacage> tomh, the beginning of summer :)<br />
<lacage> I am still waiting for it...<br />
<tomh> lacage, we have two more days of winter then you should be happier<br />
<lacage> yeah, I saw the WE forecast<br />
<tomh> lacage, I added a SocketsDefault class last night<br />
<tomh> if you think there is a cleaner approach, we can look at it<br />
<fw_> lacage: yeah<br />
<fw_> lacage: already talked to him about nsc integration stuff.<br />
<lacage> tomh, as I replied, I think that attributes would work.<br />
<hgntmp> I must leave now - for additional info regarding my person I will read the IRC backlog afterwards<br />
<lacage> hgntmp, ok. have a good night<br />
<hgntmp> or email! ;)<br />
<hgntmp> 5:46pm<br />
<lacage> fw_, were you able to setup a regular meeting ? or is this just a couple of emails ?<br />
<fw_> emails and jabber<br />
* hgntmp (i=50f62021@gateway/web/ajax/mibbit.com/x-94ba2ca630b3953c) has left #ns-3<br />
<fw_> at the moment i send him a weekly status report<br />
<tomh> lacage, well, I am not going to hold up my post to ns-developers for that (which I'm trying to write in parallel to this chat)<br />
<lacage> fw_, ok. if you can and if he is ok with it, it might make sense to send it to ns-dev.<br />
<lacage> tomh, certainly. I will comment on the list.<br />
<tomh> I have not pulled the raw buffer variants. That will still be controversial despite what we discussed on Friday. I would prefer to let it lie.<br />
<lacage> what does "let it lie" means ?<br />
<lacage> does it mean that you do not want to do it _now_ ? or that you do not want to do it _ever_ ?<br />
* lacage is curious<br />
<tomh> not reopen the issue<br />
<tomh> I will comment it on the list<br />
<lacage> ok<br />
<lacage> thanks<br />
<tjkopena> ok guys, have to run; will chat later. thx<br />
* Disconnected ().<br />
</pre></div>Tjkopena