Re: [riot-devel] Plans for switching over to a new network infrastructure in GNRC
Hi, FYI there is a re-integration PR now: https://github.com/RIOT-OS/RIOT/pull/7925 Cheers, Martine 2017-10-27 17:56 GMT+02:00 Martine Lenders : > Hi all, > > after the release is before the release, so let's use the drive to > continue the good work. > > Some of you might have noticed, that we are currently working on a big > switch-over for GNRC-internal APIs, so if you are not involved in any > direct GNRC programming or need access to the network interfaces this won't > most likely only affect you a little bit (the calls how to get an interface > ID will change -- actually simplify ;-)) to not at all. > > This is quite a massive step, since basically most of the files that are > doing operations on, or related to network interfaces (i.e. IPv6, 6LoWPAN, > MAC and routing protocols) need to be touched. In addition we decided to > integrate this network interface layer directly with the new, shiny and > fixed neighbor discovery which saves us a lot of integration work into old > stuff, but doesn't make things easier. Some of that work is already done > and in master, but most of it will take some time to adapt. > > This is why we (the RIOT maintainers) decided to go a slightly different > route than usual: we made a feature branch where all the integration work > (and testing) for the new components will happen [1] and made a 1-2 week > plan to get this branch re-merged into master as fast as possible. In that > time this feature branch exist merging new changes to GNRC into master is > highly discouraged to not risk merge conflicts in the > gnrc_netif2_integration/master branch. We will notify you again when this > embargo is lifted. > > So what changes after all this is done (I call the new interface API > gnrc_netif2 here, but in the final result it will be called just > gnrc_netif): > > * Network interfaces: > - Simplification of GNRC's network interface architecture: currently > there are 4 APIs (gnrc_netdev, gnrc_netif, gnrc_ipv6_netif, and > gnrc_sixlowpan_netif) that represent network interfaces in some kind or > form. This makes things complicated if you need e.g. in NDP information > that is both device dependent (e.g. link-layer address) and IPv6 dependent > (e.g. IPv6 address). This is why gnrc_netif2 merges all these APIs into one > single API. > - Tighter integration into GNRC's principles: For most device related > options interfaces worked like any other GNRC module and used NETAPI, but > when it came to other stuff, like IPv6 addresses or 6LoWPAN configuration, > other APIs were used. With gnrc_netif2 all options can be set via NETAPI. > - Better thread synchronization: apart from the the fact that > GNRC-externally the options are now set over NETOPT (i.e. in the thread > context of the interface) we also use recursive mutexes GNRC-internally now > to better synchronize the access to the interface. In the previous > implementation normal mutexes were used (requiring some dangerous unlocking > in the middle of an operation) or no mutexes were used at all. > - Easier to extend: If you want to provide a new MAC protocol to GNRC > you don't have to copy all the thread-handler stuff anymore. Just implement > the operations provided in `gnrc_netif2_ops_t` and let gnrc_netif2 do the > rest ;-). > * new neighbor discovery: > - In comparison to the old neighbor discovery the new was designed > more thoughtfully so it easier to maintain. > - Most issues with the old neighbor discovery were fixed (because with > the new design we actually were able to pinpoint issues within minutes, not > within days as with the old NDP) > - For the end-user the shell commands will change slightly: > manipulations of the neighbor cache and FIB now are done using the `nib` > command instead of a wide variety of commands. > > I hope that's all. > > If you have further questions, don't be afraid to ask. > > Cheers, > Martine > > [1] https://github.com/RIOT-OS/RIOT/tree/gnrc_netif2_integration/master > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes
Hi Cenk, 2017-11-01 11:05 GMT+01:00 Cenk Gündoğan : > > > On 17-10-31 18:03:01, Francisco Javier Acosta Padilla wrote: > > > […] > > > > P.S: @Martine, can you set up the next Hack&ACK meeting? Thanks > > > > > > > Anything different to do than the usual ad-hoc placecam set-up? > > > > Jup, provide a working mic for the FU's PlaceCam laptop this time (: > We had... the problem was that the machine we ran placecam on was so slow and old that ALSA wasn't able to stream that audio including video ^^ (that's definitely a problem we need to solve until next week). Cheers, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes
Hi! On 1 November 2017 at 08:53:01, Cenk Gündoğan (list-r...@cgundogan.de) wrote: Hi Paco! Just a few minor hints inlined below. On 17-10-31 18:03:01, Francisco Javier Acosta Padilla wrote: > Hi RIOT developers, maintainers, > > Maybe some attendants to the RIOT Summit 2017 remember that we have talked > about having developer/maintainer meetings from time to time to discuss about > organisational stuff, e.g. which Issues/PRs are priorities and who’s looking > at them. > > Well, I just moved a step forward into this and ask all of you to attend the > first meeting. For strategical reasons, we’ll hold these meetings one day > before the Hack&ACK, which takes place last Thursday every month. This way we > can agree which PRs/issues are likely to be solved during the Hack&ACK, > especially if the couple maintainer/commiter attend the meeting. However, > this is not limited to the Hack&ACK and can be done at any time, we’ll > discuss the way we want to work on this and if a meeting per month is > enough/too much. CG: I assume you meant every last *Tuesday* of the month, not *Thursday* Yes, I made a mistake, Hack&ACK is on Tuesday. > > I have organised this using github projects[1], on which I have created > several (maybe too much, to be discussed): > > - Bug tracker for the release -> This project keeps track of the bugs > reported in the current release. The goal is to work on them as much/soon as > possible. The first task would be to order them by priority, since for now > they’re just ordered by date. > > - A project for each area on our roadmap -> Keeps track of the current work > being done in a given area. The goal is to create issues/PRs and organise > them by priority. A maintainer will be assigned to get the issue solved/PR > merged. > > - Monthly meetings organisation -> Keeps tracking of the activities > regarding our roadmap. I think this can be used mostly to agree on which > parts of the roadmap we want to work on, and who’s steering the activities. I > didn’t add the bug tracker here but it’s maybe convenient, though it can bee > too large. > > Given that today is a holiday in Germany, and most of the > attendants/organisers of Hack&ACK are from there, there’s none today. We have > agreed that we will move it to the next Tuesday. > > Therefore, I suggest to have our first meeting next Monday. I don’t know > about the hour, since we have contributors from all over the world, but I > guess around 17:00 can fit most time zones. CG: So the first meeting is scheduled at 5 pm (CET) on November 6. For now I would say so (forgot to specify the time zone, thanks), unless most of the interested people cannot do it for that date/hour. My intention was actually to get a consensus on that matter. > > I expect your feedback and let’s also discuss about which mean can we meet. > We’re using placecam for the Hack&ACK which works more or less good, but if > we can have something better and all people is able to configure it we should > move to it. CG: I have no strong opinion about the software. If PlaceCam works then just use that. An alternative could be WebEx. Cheers, Cenk > > Since this would be our first meeting, I’d say we’ll need to reserve around > 1h for it, but I’ll try to keep the next ones no longer than 30min. > > Keep RIOTing! Cheers! > > P.S: @Martine, can you set up the next Hack&ACK meeting? Thanks! > > -- > Francisco Javier Acosta Padilla > Research Engineer at INRIA Saclay > INFINE Team > > [1] https://github.com/RIOT-OS/RIOT/projects > ___ > Maintainer mailing list > maintai...@riot-os.org > https://lists.riot-os.org/mailman/listinfo/maintainer -- Cenk Gündoğan Hamburg University of Applied Sciences Dept. of Computer Science / Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49 40 42875 - 8426 Mail: cenk.guendo...@haw-hamburg.de Web: https://www.inet.haw-hamburg.de/ ___ Maintainer mailing list maintai...@riot-os.org https://lists.riot-os.org/mailman/listinfo/maintainer ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes
Hey Martine, On 17-11-01 10:57:10, Martine Lenders wrote: > Hi, > > 2017-11-01 8:52 GMT+01:00 Cenk Gündoğan : > > > On 17-10-31 18:03:01, Francisco Javier Acosta Padilla wrote: > > […] > > > P.S: @Martine, can you set up the next Hack&ACK meeting? Thanks > > > > Anything different to do than the usual ad-hoc placecam set-up? > Jup, provide a working mic for the FU's PlaceCam laptop this time (: Cheers, Cenk > Cheers, > Martine > ___ > Maintainer mailing list > maintai...@riot-os.org > https://lists.riot-os.org/mailman/listinfo/maintainer -- Cenk Gündoğan Hamburg University of Applied Sciences Dept. of Computer Science / Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49 40 42875 - 8426 Mail: cenk.guendo...@haw-hamburg.de Web: https://www.inet.haw-hamburg.de/ signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes
Hi, 2017-11-01 8:52 GMT+01:00 Cenk Gündoğan : > On 17-10-31 18:03:01, Francisco Javier Acosta Padilla wrote: > […] > > P.S: @Martine, can you set up the next Hack&ACK meeting? Thanks > Anything different to do than the usual ad-hoc placecam set-up? Cheers, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes
Hi Paco! Just a few minor hints inlined below. On 17-10-31 18:03:01, Francisco Javier Acosta Padilla wrote: > Hi RIOT developers, maintainers, > > Maybe some attendants to the RIOT Summit 2017 remember that we have talked > about having developer/maintainer meetings from time to time to discuss about > organisational stuff, e.g. which Issues/PRs are priorities and who’s looking > at them. > > Well, I just moved a step forward into this and ask all of you to attend the > first meeting. For strategical reasons, we’ll hold these meetings one day > before the Hack&ACK, which takes place last Thursday every month. This way we > can agree which PRs/issues are likely to be solved during the Hack&ACK, > especially if the couple maintainer/commiter attend the meeting. However, > this is not limited to the Hack&ACK and can be done at any time, we’ll > discuss the way we want to work on this and if a meeting per month is > enough/too much. CG: I assume you meant every last *Tuesday* of the month, not *Thursday* > > I have organised this using github projects[1], on which I have created > several (maybe too much, to be discussed): > > - Bug tracker for the release -> This project keeps track of the bugs > reported in the current release. The goal is to work on them as much/soon as > possible. The first task would be to order them by priority, since for now > they’re just ordered by date. > > - A project for each area on our roadmap -> Keeps track of the current work > being done in a given area. The goal is to create issues/PRs and organise > them by priority. A maintainer will be assigned to get the issue solved/PR > merged. > > - Monthly meetings organisation -> Keeps tracking of the activities > regarding our roadmap. I think this can be used mostly to agree on which > parts of the roadmap we want to work on, and who’s steering the activities. I > didn’t add the bug tracker here but it’s maybe convenient, though it can bee > too large. > > Given that today is a holiday in Germany, and most of the > attendants/organisers of Hack&ACK are from there, there’s none today. We have > agreed that we will move it to the next Tuesday. > > Therefore, I suggest to have our first meeting next Monday. I don’t know > about the hour, since we have contributors from all over the world, but I > guess around 17:00 can fit most time zones. CG: So the first meeting is scheduled at 5 pm (CET) on November 6. > > I expect your feedback and let’s also discuss about which mean can we meet. > We’re using placecam for the Hack&ACK which works more or less good, but if > we can have something better and all people is able to configure it we should > move to it. CG: I have no strong opinion about the software. If PlaceCam works then just use that. An alternative could be WebEx. Cheers, Cenk > > Since this would be our first meeting, I’d say we’ll need to reserve around > 1h for it, but I’ll try to keep the next ones no longer than 30min. > > Keep RIOTing! Cheers! > > P.S: @Martine, can you set up the next Hack&ACK meeting? Thanks! > > -- > Francisco Javier Acosta Padilla > Research Engineer at INRIA Saclay > INFINE Team > > [1] https://github.com/RIOT-OS/RIOT/projects > ___ > Maintainer mailing list > maintai...@riot-os.org > https://lists.riot-os.org/mailman/listinfo/maintainer -- Cenk Gündoğan Hamburg University of Applied Sciences Dept. of Computer Science / Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49 40 42875 - 8426 Mail: cenk.guendo...@haw-hamburg.de Web: https://www.inet.haw-hamburg.de/ signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
