From 5bd36fdff16871eb7d06fc26cac07e7f2703432b Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 29 Nov 2012 01:33:22 +0100 Subject: IRC. --- community/gsoc/2012/virt/discussion.mdwn | 173 +++++++++++++++++++++++++++++++ community/gsoc/project_ideas.mdwn | 5 +- community/gsoc/project_ideas/smp.mdwn | 16 +++ 3 files changed, 192 insertions(+), 2 deletions(-) create mode 100644 community/gsoc/project_ideas/smp.mdwn (limited to 'community/gsoc') diff --git a/community/gsoc/2012/virt/discussion.mdwn b/community/gsoc/2012/virt/discussion.mdwn index 31b9ce01..e0085322 100644 --- a/community/gsoc/2012/virt/discussion.mdwn +++ b/community/gsoc/2012/virt/discussion.mdwn @@ -214,3 +214,176 @@ License|/fdl]]."]]"""]] or these meetings won't be as useful as they could be Yes. But also please don't wait for the meetings, but ask questions throughout the week, too. + + +# IRC, freenode, #hurd, 2012-08-09 + + hey, does anyone knows the network device interface well? + I don't get it by reading net_io.c/h in gnumach + nowhere_man: ask your question + nowhere_man: http://www.sceen.net/~rbraun/pcap-hurd.c <- this may + help + I don't see what the entry point is + I finally understood that I actually don't need to touch + pfinet for gsoc project + but I should do a replacement network device instead + is the net_io_init function called at start? + what entry point ? + and you should perhaps have a look at the eth-multiplexer by + zhengda + yes net_io_init is called at startup + nowhere_man: did you find your answers about networking ? + no, I'm still digging in mach's code + nowhere_man: well keep asking :/ + you left conversation without notice :/ + nowhere_man: and why mach ? + I thought hardware devices are there + nowhere_man: You wanted to push your documentation one/two + weeks ago. Why has that not yet happened? + nowhere_man: they used to be there, they are now in netdde, but in + both case it's just a matter of the same RPC interface + tschwinge: I spent very few time this week on gsoc, and + completely forgot about the push on savannah + nowhere_man: i told you to look at the work by zhengda concerning + eth-multiplexer, did you do that ? + nowhere_man: You realize GSoC is meant to be a full-time job? + Or, next to full-time? + it's full-time normally + the payment is justified by that + nowhere_man: most RPC operations you need to know about network can + be seen at work in pfinet/ethernet.c, wherever "ether_port" appears + i.e. device_open, set_filter, write, set/get_status + again, http://www.sceen.net/~rbraun/pcap-hurd.c should guide you + pretty well + since it's the very least necessary to use that interface + nowhere_man: How, roughly but realistically, are your plans to + continue this task? + nowhere_man: What has been blocking you this week so you + couldn't work on your task? + tschwinge: mostly a previous work that was supposed to end at + the beginning of the summer and only went online now, for which I'm + basically sysadmin + 21:25 < tschwinge> nowhere_man: How, roughly but realistically, + are your plans to continue this task? + this question is really more interesting actually + right now, I want to write a netword device that just sends + its frames by IPC + why ? + as I never wrote any program using Mach's IPC, that seems the + easiest to get them right + you won't have time + 21:22 < braunr> nowhere_man: i told you to look at the work by + zhengda concerning eth-multiplexer, did you do that ? + braunr: not yet, no + well that's your best chance to make some progress + braunr: is writing the virtal network device that hard? + basically, it allows "bridgind" the pfinet instances of various + subhurds + the virtual network device you want *is* eth-multiplexer + nowhere_man: GSoC is nearly over. That's why I'm asking how + this task is going to continue. I'm sorry but I reckon you have not + spend anywhere near the amount of hours that are meant to be spent on it. + and from what antrik told me, yes it's hard, and moreover, why + rewrite it if it already exists and you're late + i agree + tschwinge: I know, I've started way too late because of my + second round of exams + nowhere_man: OK, that's how you started. But how is it going + to continue... + tschwinge: in short, I write a prototype that just starts a + subhurd, and when that works correctly I add the network + nowhere_man: I mean from an organizational point of view. + well, between now and the beginning of september, I'll work + full-time on this + up until september 8th + + +# IRC, freenode, #hurd, 2012-08-09 + + nowhere_man: you do *not* have to do a replacement network + device. zhengda did that years ago. + nowhere_man: also note that zhengda also implemented the support + for *using* the virtual network device (in fact any replacement devices + -- except that no others actually exist yet) in boot + which is already in, actually, isn't it? + youpi: hm, yes... it was the patch that zhengda posted on the list + once, but later updated, and at some later point you merged the outdated + variant from the list... + outdated? + ah, but he never posted the updated one, and it got lost in git + repos, right? + (what was updated actually?) + he changed the option name and description later for more + clarity. don't remember whether there were other changes + -f, --device=device_name=device_file + Specify a device file used by subhurd + and its + virtual name. + that's the one from the Debian package + -m, --device-map=DEBICENAME=DEVICEFILE + Map the device in subhurd to the + device in the + main Hurd. + that's the one I have locally built from his tree + so you actually have access to his tree? + uhm... I used to... it was on flubber + + +# IRC, freenode, #hurd, 2012-08-18 + + so, this week I discovered how fun it is to work on a + non-mainstream OS + I hoped to start coding the tool itself, put together the + skeleton, but every Lisp implementation I tried had problems + ah you want to write it in lisp ? + ECL, that I had ported a few years ago, actually FTBFS since + I hoped to be able, it would be easier for me + and when I tried Scheme, I started with Guile (it's GNU's own + Scheme implementation, after all) + and when I execute the FFI functions, to access functions in + libmachdec + I get SIGILL + i can't advise you about anything lisp related + the most reliable thing you'll find on the hurd is C + I tried to debug that, but running Guile in GDB gets me a + SIGSEV + I'll try to make ECL to build again + this seems like a waste of time to me + avoid spending time on anything that isn't directly related to + your goal if you still hope to finish it + I'm ten times more comfortable coding in Lisp + it doesn't matter, you're late + yeah, I know, so taking the time to correct that problem + won't change the fact that I won't finish in time + so I'll finish anyway, and in Lisp + and if you lack something else, like some mach/hurd specific lisp + bindings, you'll have to spend more time on that + ok + do you know if someone had a SIGILL situation on Hurd in the + past? + I'm wondering if that's a known kind of issue + there are lots of issues + especially when it comes to other languages and runtime + environments + but is it like MAX_PATH_LEN, something that is known to + happen when porting something on Hurd? + i'm not sure how comparable it is + i'd say it's often before of the conformance issues of the hurd + because* + like missing bits of POSIX ? + or simple wrong for some corner cases + simply* + nowhere_man, I was able to run guile on my hurd image through qemu + but I didn't make any complexe programms to check if everything + works fine + yeah, it runs fine + FFI functions get you a SIGILL + + http://www.gnu.org/software/guile/manual/html_node/Dynamic-FFI.html + the define-module form at the beginning triggers the signal + nowhere_man: what do you want to implement in Lisp? + BTW, the guy working on Lisp bindings a couple of years ago used + Clisp + it was working back then + antrik: the program that sets up a subhurd + I always forget about clisp, I'll try it right away diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn index 8ce10ffa..9d486b00 100644 --- a/community/gsoc/project_ideas.mdwn +++ b/community/gsoc/project_ideas.mdwn @@ -1,5 +1,5 @@ -[[!meta copyright="Copyright © 2008, 2009, 2010, 2011 Free Software Foundation, -Inc."]] +[[!meta copyright="Copyright © 2008, 2009, 2010, 2011, 2012 Free Software +Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -87,6 +87,7 @@ other: language_bindings, gnat, gccgo, perl_python. --> [[!inline pages="community/gsoc/project_ideas/tcp_ip_stack" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/nfs" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/pthreads" show=0 feeds=no actions=yes]] +[[!inline pages="community/gsoc/project_ideas/smp" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/sound" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/disk_io_performance" show=0 feeds=no actions=yes]] [[!inline pages="community/gsoc/project_ideas/vm_tuning" show=0 feeds=no actions=yes]] diff --git a/community/gsoc/project_ideas/smp.mdwn b/community/gsoc/project_ideas/smp.mdwn new file mode 100644 index 00000000..e17c2ccf --- /dev/null +++ b/community/gsoc/project_ideas/smp.mdwn @@ -0,0 +1,16 @@ +[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!meta title="SMP"]] + + +# IRC, freenode, #hurd, 2012-09-30 + + i expect smp to be our next gsoc project -- cgit v1.2.3