From mirageos-devel-bounces@lists.xenproject.org Thu Mar 07 11:32:04 2024 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Mar 2024 11:32:04 +0000 Received: from list by lists.xenproject.org with outflank-mailman.689786.1075088 (Exim 4.92) (envelope-from ) id 1riByb-0004ud-KX; Thu, 07 Mar 2024 11:31:53 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 689786.1075088; Thu, 07 Mar 2024 11:31:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1riByb-0004uW-HN; Thu, 07 Mar 2024 11:31:53 +0000 Received: by outflank-mailman (input) for mailman id 689786; Thu, 07 Mar 2024 11:31:52 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1riByZ-0004Nd-Bk for mirageos-devel@lists.xenproject.org; Thu, 07 Mar 2024 11:31:51 +0000 Received: from wfout6-smtp.messagingengine.com (wfout6-smtp.messagingengine.com [64.147.123.149]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 48f23a00-dc76-11ee-afda-a90da7624cb6; Thu, 07 Mar 2024 12:31:50 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfout.west.internal (Postfix) with ESMTP id C91F71C00081 for ; Thu, 7 Mar 2024 06:31:47 -0500 (EST) Received: from imap46 ([10.202.2.96]) by compute5.internal (MEProxy); Thu, 07 Mar 2024 06:31:47 -0500 Received: by mailuser.nyi.internal (Postfix, from userid 501) id C03FF2A2008B; Thu, 7 Mar 2024 06:31:46 -0500 (EST) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" X-Inumbo-ID: 48f23a00-dc76-11ee-afda-a90da7624cb6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=v0.no; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s= mesmtp; t=1709811107; x=1709897507; bh=Xv+8q/sFHfMpzjinEv7KbmU9H cn/J181mYXbsUuyMl8=; b=vD9yuR21wRKudIL5bXVXOdIA1V0eV+OU1qRZ4Lx4B dCz70XZs3Pu68e7Kz+eQJdzrZAURhmAT3ZbKHmy/bSuY6/GvFEqVdypjwVm3NlvW LMttzAuXEyw7PgRET7eHXX4KOwzdH+3QfnHOIu1Egrvd9U3WBppgxMQpQdSEAE2e 6s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1709811107; x=1709897507; bh=Xv+8q/sFHfMpzjinEv7KbmU9Hcn/J181mYX bsUuyMl8=; b=YQPuty61gVVi0TSIVlKPX8KEVs9EumPjdcsP5XM9oCJC0buEdZu xLHaRy3HIhv91v1iMzswXAIME960Q0ur+LKfyTdnDm1kIvmZ0eGn4o39lx5F07u0 EVHZCSs5mpzmzmfKuKQQYITXfR43GdSrtSlvPo3OgxDSam8hqf5RUoxWCg2iCMMo YC2rTgxnwFs4cwvKqFFHxmRG0+SnSElO/GtP1jdWQV65KE7QFBIvUsSdT66yEhNE 9G0ObyXtRwElMv0fg27lcUnAAEs9Ee37vc5cLYZgwSr1cvnvmExrapD9i+ruCLo8 9ijGwn2QIepjUVWrkMgOZUn/mbmlX3OFB8w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrieefgddvlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesthdtredtre ertdenucfhrhhomhepfdforghgnhhushcuufhkjhgvghhsthgrugdfuceomhgrghhnuhhs sehvtddrnhhoqeenucggtffrrghtthgvrhhnpeetveeuuedvueetiedtudeuhedvteejud fhfeetvdejhedukedvuefgffdvjeejvdenucffohhmrghinhepuggrthgrrdgtohhophdp jhhithdrshhinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepmhgrghhnuhhssehvtddrnhho X-ME-Proxy: Feedback-ID: i11304080:Fastmail X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-251-g8332da0bf6-fm-20240305.001-g8332da0b MIME-Version: 1.0 Message-Id: <1067fee6-a01a-46bc-a9af-2f6a260d6b72@app.fastmail.com> Date: Thu, 07 Mar 2024 12:31:25 +0100 From: "Magnus Skjegstad" To: mirageos-devel@lists.xenproject.org Subject: MirageOS meeting 2024-03-11 - 9:00 CET Content-Type: text/plain Hi everyone, The next MirageOS meeting will be Monday March 11th at 9:00-10:00 CET. Everyone is welcome to attend this bi-weekly meeting. It's a good opportunity to meet others working on MirageOS, discuss current or future projects or PR review. The current agenda is here: https://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA We have some items that carried over from last time, but feel free to add any additional items you'd like to discuss. The Jitsi link for the meeting is https://meet.jit.si/mirageos-call -- Magnus From mirageos-devel-bounces@lists.xenproject.org Mon Mar 11 07:57:29 2024 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Mar 2024 07:57:29 +0000 Received: from list by lists.xenproject.org with outflank-mailman.691220.1076944 (Exim 4.92) (envelope-from ) id 1rjaX3-0003oz-So; Mon, 11 Mar 2024 07:57:13 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 691220.1076944; Mon, 11 Mar 2024 07:57:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rjaX3-0003os-Q1; Mon, 11 Mar 2024 07:57:13 +0000 Received: by outflank-mailman (input) for mailman id 691220; Mon, 11 Mar 2024 07:57:12 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rjaX1-0003om-L8 for mirageos-devel@lists.xenproject.org; Mon, 11 Mar 2024 07:57:12 +0000 Received: from fout1-smtp.messagingengine.com (fout1-smtp.messagingengine.com [103.168.172.144]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id f50c69b7-df7c-11ee-a1ee-f123f15fe8a2; Mon, 11 Mar 2024 08:57:09 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfout.nyi.internal (Postfix) with ESMTP id 22B6913800C1 for ; Mon, 11 Mar 2024 03:57:07 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute5.internal (MEProxy); Mon, 11 Mar 2024 03:57:07 -0400 Received: by mailuser.nyi.internal (Postfix, from userid 501) id D174E2A2008B; Mon, 11 Mar 2024 03:57:06 -0400 (EDT) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" X-Inumbo-ID: f50c69b7-df7c-11ee-a1ee-f123f15fe8a2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=v0.no; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=mesmtp; t=1710143827; x=1710230227; bh=usot99g aFPQw+s+ZkEjPiZNes+Wx83l09Nsak5PL9Nk=; b=Ux2AGgOYA3l8SmPelSIXTgI rHmxwgPgrNht3YOr3JGnQpFPgXnzI9uFL0AByS+arWmE8p+bvkChmq6YzobQgGBo +sdv4uQdfCLkro3c/rnmsO/MGgjMF/gbkbfbRcLdvdKeQGyLYjLNyiqMczJH6FTh 07MhV1WK0I4/OoY3H3lc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1710143827; x=1710230227; bh=usot99gaFPQw+s+ZkEjPiZNes+Wx 83l09Nsak5PL9Nk=; b=LktovckaywcpGuUzKFfdF7g8T/9EnkTvFEHykJXsMkBy 3CIcS4LYmMnL7XyfLX7RtDbi1FtJrK3xtdSTv/QixoqS6VDGmo+M+RADfWfvMEAn B5aDl9z+RdErMGYpOhXsOL3I/5Gtlqz4I3BcHWgVlEfFTzX4NZ1D8qERkKtCWZRO ARUfyP1UJLort8vLmWrots/CGBV6PAqUJjU4wG8nYjOGOFA+pRYZuaReNVVmTc6K OJuPcL7zjtUmuvV9+O+TvCYzP+0hpXtyFRWafLbLKKZ3NKRDdSyvUKHE1V0DHsUJ MeMW2l18kzHhsaKKZQ/ZTjSVNRRn9UAkMuYOkdHohQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjedtgdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrghhnuhhsucfukhhjvghgshhtrggufdcuoehmrghg nhhushesvhdtrdhnoheqnecuggftrfgrthhtvghrnhepgeelhfdtleefhfevjeffudefie egjeduffdthfeigfelteegheeikeetueeuueevnecuffhomhgrihhnpegurghtrgdrtgho ohhppdhjihhtrdhsihenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmrghgnhhushesvhdtrdhnoh X-ME-Proxy: Feedback-ID: i11304080:Fastmail X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-251-g8332da0bf6-fm-20240305.001-g8332da0b MIME-Version: 1.0 Message-Id: <311b13d5-a369-4548-9d54-ca1dcb8cebd7@app.fastmail.com> In-Reply-To: <1067fee6-a01a-46bc-a9af-2f6a260d6b72@app.fastmail.com> References: <1067fee6-a01a-46bc-a9af-2f6a260d6b72@app.fastmail.com> Date: Mon, 11 Mar 2024 08:56:46 +0100 From: "Magnus Skjegstad" To: mirageos-devel@lists.xenproject.org Subject: Re: MirageOS meeting 2024-03-11 - 9:00 CET Content-Type: text/plain Reminder, the MirageOS meeting is starting in a few minutes. Agenda: https://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA Meeting link: https://meet.jit.si/mirageos-call See you there, Magnus On Thu, 7 Mar 2024, at 12:31, Magnus Skjegstad wrote: > Hi everyone, > > The next MirageOS meeting will be Monday March 11th at 9:00-10:00 CET. > > Everyone is welcome to attend this bi-weekly meeting. It's a good > opportunity to meet others working on MirageOS, discuss current or > future projects or PR review. > > The current agenda is here: https://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA > > We have some items that carried over from last time, but feel free to > add any additional items you'd like to discuss. > > The Jitsi link for the meeting is https://meet.jit.si/mirageos-call > > -- > Magnus From mirageos-devel-bounces@lists.xenproject.org Mon Mar 11 14:19:06 2024 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Mar 2024 14:19:06 +0000 Received: from list by lists.xenproject.org with outflank-mailman.691520.1077555 (Exim 4.92) (envelope-from ) id 1rjgUR-0003nt-MZ; Mon, 11 Mar 2024 14:18:55 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 691520.1077555; Mon, 11 Mar 2024 14:18:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rjgUR-0003nm-JX; Mon, 11 Mar 2024 14:18:55 +0000 Received: by outflank-mailman (input) for mailman id 691520; Mon, 11 Mar 2024 14:18:53 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rjgUP-0003mH-DK for mirageos-devel@lists.xenproject.org; Mon, 11 Mar 2024 14:18:53 +0000 Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [2a00:1450:4864:20::629]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 48553973-dfb2-11ee-a1ee-f123f15fe8a2; Mon, 11 Mar 2024 15:18:50 +0100 (CET) Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-a45cdb790dfso461568166b.3 for ; Mon, 11 Mar 2024 07:18:50 -0700 (PDT) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" X-Inumbo-ID: 48553973-dfb2-11ee-a1ee-f123f15fe8a2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710166730; x=1710771530; darn=lists.xenproject.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PAJbEV+gCiwsfdVlAf7wLoj6UxLL1cMQCC6wZzG8JiQ=; b=ar2ZNnThaet96Pv49jBHwWEfi9T3kC2vdCNgO+LRForkK29JFStpJVTTelbvY/jCoG d4tHsvuDNMraapb7Jdk8ry+lirzeK9lp/+8wchQC+Ohcr19aZj3V1IiqNF4AgShWVQQN F9XTfft9WJ0wBWmsf6CK0CE4qHsEncQvaHdrm4KCsMhbfbYlLe/aXq1p3+fIRmX42XfY viKNCKYvGWGGMgt3sWiet2QY3SQPPNFGqH81ja44yXx6Y6AkFHgy4iVTgJPCxSmnfpm5 cu5PLzk1vtjCFbQ95AloFHwH+EFBzOjIC2uozqJbDy3MDivmClSfpxJ0Rjgn0yKtr6OM jxvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710166730; x=1710771530; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PAJbEV+gCiwsfdVlAf7wLoj6UxLL1cMQCC6wZzG8JiQ=; b=j090YHL/r2zLJiDo3RBQnmEynbi5zneAoIC1fDveaDVtby1q094TVQtak9MTPN/q3K 9CUbFhL1rjLyTo/pTo0cL7hJveCalA1J7IQvcwqRbtAQu7ZRH0AWhOhMqRncWi9Mycq/ dsUkl6XuPjjDUhC2ZkpISbZucWWycU3EKDo5yX/NOQf5icZ2xCuKvOYN9hRunnqZudiW nYF6DaCC8wmgd9sr4L33nLS1gU9KeW6GkzWBuatELiWVl7mxFi1NgznAp/HWSyVQIZYA 9gbtDD27fPy8ev1JgS6Q4uaVugbPwqHU+XVrZkXMEexMoKAwBpi88qPnduj86TAn8Sxx lcNA== X-Gm-Message-State: AOJu0YySP8eUGlGE3bsumg5QlTdQTdG3nuKTopVon4K7MOHIgNV7RdVJ js2HNHeclyz+PH/X3jahtuirgb1i+EbhAPfru2cVOplRRITw0qtX+PyRFAcJTVMqZUrDHX1gIVd C72zHHqlAFlRstcvSDWPWnBH+bVPANPHaSTn3cQ== X-Google-Smtp-Source: AGHT+IGsgkFyPEeUZQqZxL0UErxkrNuD5TSL9Fz8rfWAHocF2tLkdLIz9TCNzkXsfajl03s2aqke2kpjGVRHcpIkXv0= X-Received: by 2002:a17:907:2d11:b0:a45:abec:cff4 with SMTP id gs17-20020a1709072d1100b00a45abeccff4mr5196006ejc.32.1710166729574; Mon, 11 Mar 2024 07:18:49 -0700 (PDT) MIME-Version: 1.0 References: <1067fee6-a01a-46bc-a9af-2f6a260d6b72@app.fastmail.com> <311b13d5-a369-4548-9d54-ca1dcb8cebd7@app.fastmail.com> In-Reply-To: <311b13d5-a369-4548-9d54-ca1dcb8cebd7@app.fastmail.com> From: Romain Calascibetta Date: Mon, 11 Mar 2024 15:18:38 +0100 Message-ID: Subject: Re: MirageOS meeting 2024-03-11 - 9:00 CET To: Magnus Skjegstad Cc: mirageos-devel@lists.xenproject.org Content-Type: multipart/alternative; boundary="0000000000006c5aa906136338b9" --0000000000006c5aa906136338b9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable This is the report of the MirageOS meeting (as available here: https://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA?both) # MirageOS community call ### 25/03/2024 (next) - What do we want Mirage5 to look like? And when do we want to make a release? - runtime args - Ocaml 5 support - dune pkg? - No more Lwt? ### 11/03/2024 - Present: Kaushik, Samuel, dinosaure, Magnus, Pierre, Alfred, Thomas, Hannes, Shakthi. - PR review - new API for runtime arguments: https://github.com/mirage/mirage/pull/1493 -- ready to merge. Late feedback is useful, please test and review if possible - plan is to merge today. After it's merged it's also possible to make changes (although before merge is better) - solo5+ocaml5: https://github.com/mirage/ocaml-solo5/pull/124 - samuel had sound issues, post update on pr and discuss next time - current state: reworked the build process and moved to support OCaml 5.2, not yet ready for a review - Unikraft+mirage plans - tarides has grant with unikraft to work with them on mirage, still early - current plan is to first look at solo5 and try to unlock what's blocking ocaml5 and look at the build system hacks and see if we can tweak them to help with unikraft integration. - see if we can reuse small C subset of unikraft instead of custom solo5 calls, starting slowly - two main blockers/unknowns; - if we use unikraft, what do we gain over solo5? Maybe performance, as we can do io without vmexit. But we don't know what we lose in terms of security. Security roadmap for unikraft, but still wip. - unikraft comes with existing tooling - have to use a cli tool to generate a small c project that contains what you need. Cli tool will link application etc. Similar to what mirage does, so we have to figure out which tools drives which part of the process. Have to think about this to get a nice user experience - goal is not to drop solo5, it's working well and we don't want to completely switch to unikraft - just want to provide a new backend and clean up solo5 bindings in the process - hannes: main goal is performance? thomas: goal is to extend the device model, want to support more types of devices - e.g. what about things like pci and gpu passthrough. This doesn't fit with the solo5 model. Performance is also interesting; if we build a unikernel focussed on performance, how much further can we go. But we don't want to lose security benefits. Unikraft has a team that maintains it and can help develop new features - magnus: timeframe? thomas: this quarter to explore, figure out what's possible. Expect to have some initial targets at end of year - magnus: new architectures? thomas: exploring what pthreads and smp can gives us with ocaml5 - alfred: what is the status of solo5, likely to evolve with pthreads? thomas: currently maintained, but smp may nto fit the philosophy of solo5. romain: I maintain solo5 and I agree that we don't want to have multicore support there, we don't have the resources to make it. Also, do we actually need multiple cores for unikernels? In my view, no, one core is enough. Would like to have ocaml5 support (with effects and so on), but multicore not important. Thomas: I think that makes sense, keep the solo5 runtime super simple for security reasons - then experiment with smp support with unikraft and mirage. - How can we improve the security story around MirageOS? What are the security issues with mirage? - thomas: when we talk about mirage, usually we say that we are more secure than other solutions; type safety and memory safety. But then a question is whether everything is ocaml, what about c bindings etc? I started aggregating a list of security features in solo5, it's important that we demonstrate that we focus on security not only in ocaml. It would be nice to have a place where we talk about security end to end in mirage. - alfred: important to document, when we had security review of includeos this would have helped us by providing context for test scripts etc - hannes: I'm also interested in the security. Several security audits of mirage, if these are public, we should link to them. Alfred, could be interesting to see the review report for includeos as well. Was also some work on improving issues in solo5 that are documented in the changelog. - thomas: yes, would be great to put what is currently documented in changelogs, PRs etc in one location - IncludeOS / Mirage - alfred: experimenting with building a high performance game server as a unikernel. Interested in iouring experiments and how to support thousands of players. Not possible currently with solo5. From current experiments seems really hard to be able to send enough data in a single process. Multicore also has a cost, so not clear that it's the only best/solution. - hannes: have you looked at the solo5 virtio code? alfred: yes, but I think you still have the functional interface where you have to do one packet at the time. Solo5 doesn't expose the ring buffers into mirage, I think you need to expose virtio to mirage or iouring. Hannes: yes, the api requires calls to send - thomas: we have sendv some places? hannes: only at the mirage-flow layer (so, TCP / TLS), not at the lower layers - solo5 netmap support: https://github.com/solo5-netmap/solo5 - VPN (hannes) - hannes: we have been working on vpn lately. working on reducing allocations, saw performance improvements also in mirage-crypto. Robur also interested in improving performance in general, but focussing on single thread first - performance numbers for MirageVPN: https://github.com/robur-coop/miragevpn/issues/206#issuecomment-1980849179 - mirage-crypto performance: https://discuss.ocaml.org/t/ann-mirage-crypto-0-11-3-with-more-speed-for-el= liptic-curves-and-the-future-roadmap-of-mirage-crypto/ and announcement (with numbers https://github.com/mirage/mirage-crypto/releases/tag/v0.11.3) - alfred: shared memory available for multiple unikernels to coordinate? hannes: not in solo5 - you could use block devices or something like that, but no real interface available - available in xen. Could be useful to add with the right usecase. Thomas: perhaps something to add outside solo5? alfred: we could do polling for high performance, then block device might work - Next meeting will be in two weeks - March 25th ### 26/02/2024 - Present: dinosaure, Pierre, Hannes, Virgile, Thomas G. Thomas L., Samuel, Shakthi, Magnus - Agenda: - Meta: - Should we use Zoom or something else? - Pierre: Some universities cannot use Zoom on Linux. - Dinosaure: Prefers to use Jitsi. - Virgile: Can use Renater (which uses Jitsi) if someone has a renater account. - Pierre-Alain will investigate. - Hannes: there is the public instance jit.si where no registration is necessary (as used e.g. in the opam-repository meetings) - Should we use https://pad.data.coop/ or something else? =3D> Pad seems good! - Anyone willing to help organising these calls? (send , taking notes, etc.) - Next meeting will be organised by Magnus :-) Thanks (and Virgile is also happy to help) - MirageOS retreat update? - 16 people signed up! early-birds registration seems to work fine - still space available - even for a few days and/or for the week-end - mix of people that have been there before, and new people! - PR updates - solo5+ocaml5: https://github.com/mirage/ocaml-solo5/pull/124 - Samuel and Fabrice are trying to revive the PR. Cleaning up the x-compiler story for the OCaml compiler in a state that could be upstream. The goal is to clean up all the pieces are glued together. Still trying to understand how the various details are working (like memory allocation). Target: OCaml 5.2 (which include compaction) as many things have changed. - Hannes: there are 2 or 3 PRs that pretend to do something with OCaml 5. Some of them have a lots of comments from Christiano and others. Is there a plan to merge/review those comments too? Some stuff implemented in C were a bit brittle. Would be sad if we lose these reviews. - Samuel: plan is probably to open a new PR that adress all of the comments (#122, #124, #129). Many things have changed in 5.2. - Dinosaure: what's the issue with x-compilation? Samuel: many ways in the way ocaml-solo5 works is to patch the OCaml build system (with a few things broken as a result). Things are very brittle. We would like to have something more solid. Dinosaure: this seems independant? Could we decouple those concerns? Samuel: indeed. currently trying to understand how things work but the idea is to reduce the maintenance as well. and to understand what is needed for solo5 vs. x-compilation. Dinosaure: see ocaml-solo5#123 (most issues are related `configure`). Samuel: will talk to Sebastien next - mirage runtime keys v2: https://github.com/mirage/mirage/pull/149= 3 - Thomas: - use cmdliner directly, instead of a custom fork - keys are split into configuration time keys and runtime keys - the runtime ones are only defined at runtime - it is a breaking big change - Hannes: - configure-time: you select what libraries you want to use in the unikernel (keys) - runtime-time: you select some runtime parameters (ip address, etc.) - better type for key - issue: type errors, locations in generated code - Happy with the current state but do not have time to review fully - Thomas: - updated existing unikernels - worked on error locations (you need to pass `__LOC__`) - there's a OCaml compiler patch that does this automatically - ~all examples and documentation will need to be updated to reflect the new interface: big workload - Hannes: can we remove the dependency between mirage and mirage-runtime - Dinosaure: the idea looks good, and the possibility to add custom types (via cmdliner) is nice - Thomas: will make progress for the next call - MirageOS relies on "opam-monorepo", what is the schedule switching to "dune pkg" (last was "Q1/2024" - anyone actively working on that)? - the dune and opam team worked for the last year to include opam-lib into dune - dune will be able to compute (make a lock file), download packages it needs locally, and compile each opam package (even if the package is not using dune) - single tool to define dependencies, whenever you modify the dune file, the opam packages are updated - rules will be cached - it is similar to opam-monorepo - packages need to be relocatable (not all are, e.g. the compiler) - there'll be a small overlay (similar to opam-monorepo overlay) for a small set of packages that are not possible to build with "dune pkg" - timeline: first alpha was planned end of Q1, now scheduled for May - what needs to be done for mirage? we haven't tested it yet. need to discuss and test once an alpha is around (thomas will test even earlier) - for now we need to keep opam-monorepo - Thomas: are there urgent pains to address? - Hannes: hard to use old versions of dunes, ... - Hannes: Is there any specification of how dune pkg will download/organize etc., for the purpose of reproducible builds? -- Thomas: it created a lock file and downloads using opam-lib - Hannes: carton/git issue with opam-monorepo -- Thomas: this will be fixed in "dune pkg" - Dune pkg milestone: https://github.com/ocaml/dune/issues?q=3Dis%3Aopen+is%3Aissue+milestone%3A%= 22Package+Management+MVP%22 - dune+orb (reproducible build integration): https://github.com/ocaml/dune/issues/9548 - Performance considerations for MirageOS (let's take mirage-crypto as example) - EC NIST curves pre-computed tables -- https://github.com/mirage/mirage-crypto/pull/191 shows a speedup of 4x - mirage-crypto symmetric cipher (AES-GCM / Poly1305-Chacha20) around 10x slower than OpenSSL (see https://github.com/mirage/mirage-crypto/pull/203, a speedup of ~2.5x for chacha using string/bytes) - cstruct.t vs bytes -- https://blog.robur.coop/articles/speeding-ec-string.html shows a speedup of 2.5x - or replace the underlying structure of cstruct from bigarrays to bytes? "Just" have to take care of IO-pages which still need aligned addresses - for Xen interfaces we need page-aligned non-moving memory areas - Dinosaure: don't use _systematically_ Cstruct=E2=80=A7t and probab= ly we should use bytes more systematically and asking ourselves about particularities of bigarray - Thomas: Patrick has started a Bstruct library: https://github.com/ocaml-multicore/ocaml-uring/pull/101 - mirage-flow + shutdown (https://github.com/mirage/mirage-flow/pull/48= ) - Hannes: released to opam-repository as mirage-flow 4.x - Hannes: anyone eager to review: https://github.com/mirage/mirage-tcpip/pull/512 - Thomas: will ping Dave - Next meeting - https://meet.jit.si/mirageos-call, 9 CET in two weeks (March 11th) ### Moved to next meeting - Unikraft+mirage plans - How can we improve the security story around MirageOS? What are the security issues with mirage? - What do we want Mirage5 to look like? - Ocaml 5 support - No more Lwt? - IncludeOS / Mirage On Mon, Mar 11, 2024 at 9:09=E2=80=AFAM Magnus Skjegstad wro= te: > Reminder, the MirageOS meeting is starting in a few minutes. > > Agenda: https://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA > Meeting link: https://meet.jit.si/mirageos-call > > See you there, > Magnus > > On Thu, 7 Mar 2024, at 12:31, Magnus Skjegstad wrote: > > Hi everyone, > > > > The next MirageOS meeting will be Monday March 11th at 9:00-10:00 CET. > > > > Everyone is welcome to attend this bi-weekly meeting. It's a good > > opportunity to meet others working on MirageOS, discuss current or > > future projects or PR review. > > > > The current agenda is here: https://pad.data.coop/wGS4r8RyTKqQ73mcw7Frw= A > > > > We have some items that carried over from last time, but feel free to > > add any additional items you'd like to discuss. > > > > The Jitsi link for the meeting is https://meet.jit.si/mirageos-call > > > > -- > > Magnus > > --=20 Romain Calascibetta - http://din.osau.re/ --0000000000006c5aa906136338b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This is the report of the MirageOS meeting (as availa= ble here: htt= ps://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA?both)

# MirageOS commu= nity call

### 25/03/2024 (next)

- What do we want Mirage5 to = look like? And when do we want to make a release?
=C2=A0 =C2=A0 - runtim= e args
=C2=A0 =C2=A0 - Ocaml 5 support
=C2=A0 =C2=A0 - dune pkg?
= =C2=A0 =C2=A0 - No more Lwt?

### 11/03/2024
- Present: Kaushik, = Samuel, dinosaure, Magnus, Pierre, Alfred, Thomas, Hannes, Shakthi.
- PR= review
=C2=A0 =C2=A0 - new API for runtime arguments: https://github.com/mirage/mirage/pull= /1493 -- ready to merge. Late feedback is useful, please test and revie= w if possible - plan is to merge today. After it's merged it's also= possible to make changes (although before merge is better)
=C2=A0 =C2= =A0 - solo5+ocaml5: https://github.com/mirage/ocaml-solo5/pull/124
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 - samuel had sound issues, post update on pr and discuss next ti= me
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - current state: reworked the build proce= ss and moved to support OCaml 5.2, not yet ready for a review
- Unikraft= +mirage plans
=C2=A0 =C2=A0 - tarides has grant with unikraft to work wi= th them on mirage, still early
=C2=A0 =C2=A0 - current plan is to first = look at solo5 and try to unlock what's blocking ocaml5 and look at the = build system hacks and see if we can tweak them to help with unikraft integ= ration.
=C2=A0 =C2=A0 - see if we can reuse small C subset of unikraft i= nstead of custom solo5 calls, starting slowly
=C2=A0 =C2=A0 - two main b= lockers/unknowns;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - if we use unikraft, what= do we gain over solo5? Maybe performance, as we can do io without vmexit. = But we don't know what we lose in terms of security. Security roadmap f= or unikraft, but still wip.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - unikraft comes= with existing tooling - have to use a cli tool to generate a small c proje= ct that contains what you need. Cli tool will link application etc. Similar= to what mirage does, so we have to figure out which tools drives which par= t of the process. Have to think about this to get a nice user experience=C2=A0 =C2=A0 =C2=A0 =C2=A0 - goal is not to drop solo5, it's working = well and we don't want to completely switch to unikraft - just want to = provide a new backend and clean up solo5 bindings in the process
=C2=A0= =C2=A0 - hannes: main goal is performance? thomas: goal is to extend the d= evice model, want to support more types of devices - e.g. what about things= like pci and gpu passthrough. This doesn't fit with the solo5 model. P= erformance is also interesting; if we build a unikernel focussed on perform= ance, how much further can we go. But we don't want to lose security be= nefits. Unikraft has a team that maintains it and can help develop new feat= ures
=C2=A0 =C2=A0 - magnus: timeframe? thomas: this quarter to explore,= figure out what's possible. Expect to have some initial targets at end= of year
=C2=A0 =C2=A0 - magnus: new architectures? thomas: exploring wh= at pthreads and smp can gives us with ocaml5
=C2=A0 =C2=A0 - alfred: wha= t is the status of solo5, likely to evolve with pthreads? thomas: currently= maintained, but smp may nto fit the philosophy of solo5. romain: I maintai= n solo5 and I agree that we don't want to have multicore support there,= we don't have the resources to make it. Also, do we actually need mult= iple cores for unikernels? In my view, no, one core is enough. Would like t= o have ocaml5 support (with effects and so on), but multicore not important= . Thomas: I think that makes sense, keep the solo5 runtime super simple for= security reasons - then experiment with smp support with unikraft and mira= ge.
- How can we improve the security story around MirageOS? What are th= e security issues with mirage?
=C2=A0 =C2=A0 - thomas: when we talk abou= t mirage, usually we say that we are more secure than other solutions; type= safety and memory safety. But then a question is whether everything is oca= ml, what about c bindings etc? I started aggregating a list of security fea= tures in solo5, it's important that we demonstrate that we focus on sec= urity not only in ocaml. It would be nice to have a place where we talk abo= ut security end to end in mirage.
=C2=A0 =C2=A0 - alfred: important to d= ocument, when we had security review of includeos this would have helped us= by providing context for test scripts etc
=C2=A0 =C2=A0 - hannes: I'= ;m also interested in the security. Several security audits of mirage, if t= hese are public, we should link to them. Alfred, could be interesting to se= e the review report for includeos as well. Was also some work on improving = issues in solo5 that are documented in the changelog.
=C2=A0 =C2=A0 - th= omas: yes, would be great to put what is currently documented in changelogs= , PRs etc in one location
- IncludeOS / Mirage
=C2=A0 =C2=A0 - alfred= : experimenting with building a high performance game server as a unikernel= . Interested in iouring experiments and how to support thousands of players= . Not possible currently with solo5. From current experiments seems really = hard to be able to send enough data in a single process. Multicore also has= a cost, so not clear that it's the only best/solution.
=C2=A0 =C2= =A0 - hannes: have you looked at the solo5 virtio code? alfred: yes, but I = think you still have the functional interface where you have to do one pack= et at the time. Solo5 doesn't expose the ring buffers into mirage, I th= ink you need to expose virtio to mirage or iouring. Hannes: yes, the api re= quires calls to send
=C2=A0 =C2=A0 - thomas: we have sendv some places? = hannes: only at the mirage-flow layer (so, TCP / TLS), not at the lower lay= ers
=C2=A0 =C2=A0 - solo5 netmap support: https://github.com/solo5-netmap/solo5
- VPN (han= nes)
=C2=A0 =C2=A0 - hannes: we have been working on vpn lately. working= on reducing allocations, saw performance improvements also in mirage-crypt= o. Robur also interested in improving performance in general, but focussing= on single thread first
=C2=A0 =C2=A0 - performance numbers for MirageVP= N: https://github.com/robur-coop/miragevpn/issues/206#issuecomm= ent-1980849179
=C2=A0 =C2=A0 - mirage-crypto performance: https://discuss.oc= aml.org/t/ann-mirage-crypto-0-11-3-with-more-speed-for-elliptic-curves-and-= the-future-roadmap-of-mirage-crypto/ and announcement (with numbers https= ://github.com/mirage/mirage-crypto/releases/tag/v0.11.3)
=C2=A0 =C2= =A0 - alfred: shared memory available for multiple unikernels to coordinate= ? hannes: not in solo5 - you could use block devices or something like that= , but no real interface available - available in xen. Could be useful to ad= d with the right usecase. Thomas: perhaps something to add outside solo5? a= lfred: we could do polling for high performance, then block device might wo= rk
- Next meeting will be in two weeks - March 25th

### 26/02/202= 4
- Present: dinosaure, Pierre, Hannes, Virgile, Thomas G. Thomas L., Sa= muel, Shakthi, Magnus
- Agenda:
=C2=A0 =C2=A0 - Meta:
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 - Should we use Zoom or something else?
=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Pierre: Some universities cannot use Zoom on = Linux.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Dinosaure: Prefers t= o use Jitsi.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Virgile: Can us= e Renater (which uses Jitsi) if someone has a renater account.
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Pierre-Alain will investigate.
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Hannes: there is the public instan= ce jit.si where no registration is necessary = (as used e.g. in the opam-repository meetings)
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 - Should we use https://pad.data.coo= p/ or something else? =3D> Pad seems good!
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 - Anyone willing to help organising these calls? (send , taking note= s, etc.)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Next meeting will b= e organised by Magnus :-) Thanks (and Virgile is also happy to help)
=C2= =A0 =C2=A0 - MirageOS retreat update?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - 16 p= eople signed up! early-birds registration seems to work fine
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 - still space available - even for a few days and/or for = the week-end
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - mix of people that have been = there before, and new people!
=C2=A0 =C2=A0 - PR updates
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 - solo5+ocaml5: https://github.com/mirage/ocaml-solo5/pull/124
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Samuel and Fabrice are trying to r= evive the PR. Cleaning up the x-compiler story for the OCaml compiler in a = state that could be upstream. The goal is to clean up all the pieces are gl= ued together. Still trying to understand how the various details are workin= g (like memory allocation). Target: OCaml 5.2 (which include compaction) as= many things have changed.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - H= annes: there are 2 or 3 PRs that pretend to do something with OCaml 5. Some= of them have a lots of comments from Christiano and others. Is there a pla= n to merge/review those comments too? Some stuff implemented in C were a bi= t brittle. Would be sad if we lose these reviews.
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 - Samuel: plan is probably to open a new PR that adres= s all of the comments (#122, #124, #129). Many things have changed in 5.2. =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Dinosaure: what's the i= ssue with x-compilation? Samuel: many ways in the way ocaml-solo5 works is = to patch the OCaml build system (with a few things broken as a result). Thi= ngs are very brittle. We would like to have something more solid. Dinosaure= : this seems independant? Could we decouple those concerns? Samuel: indeed.= currently trying to understand how things work but the idea is to reduce t= he maintenance as well. and to understand what is needed for solo5 vs. x-co= mpilation. Dinosaure: see ocaml-solo5#123 (most issues are related `configu= re`). Samuel: will talk to Sebastien next
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - = mirage runtime keys v2: https://github.com/mirage/mirage/pull/1493
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0- Thomas:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0- use cmdliner directly, instead of a custom fork
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- keys are split into confi= guration time keys and runtime keys
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0- the runtime ones are only defined at runtime
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- it is a breaking big = change
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Hannes:
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- configure-time: you select w= hat libraries you want to use in the unikernel (keys)
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- runtime-time: you select some runti= me parameters (ip address, etc.)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0- better type for key
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0- issue: type errors, locations in generated code=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Happy with the c= urrent state but do not have time to review fully
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0- Thomas:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0- updated existing unikernels
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0- worked on error locations (you need to pass `__LOC__`)
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- there's a OCaml compi= ler patch that does this automatically
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0- ~all examples and documentation will need to be updated = to reflect the new interface: big workload
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0- Hannes: can we remove the dependency between mirage and mira= ge-runtime
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Dinosaure: the ide= a looks good, and the possibility to add custom types (via cmdliner) is nic= e
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Thomas: will make progress = for the next call
=C2=A0 =C2=A0 - MirageOS relies on "opam-monorepo= ", what is the schedule switching to "dune pkg" (last was &q= uot;Q1/2024" - anyone actively working on that)?
=C2=A0 =C2=A0 =C2= =A0 =C2=A0- the dune and opam team worked for the last year to include opam= -lib into dune
=C2=A0 =C2=A0 =C2=A0 =C2=A0- dune will be able to compute= (make a lock file), download packages it needs locally, and compile each o= pam package (even if the package is not using dune)
=C2=A0 =C2=A0 =C2=A0= =C2=A0- single tool to define dependencies, whenever you modify the dune f= ile, the opam packages are updated
=C2=A0 =C2=A0 =C2=A0 =C2=A0- rules wi= ll be cached
=C2=A0 =C2=A0 =C2=A0 =C2=A0- it is similar to opam-monorepo=
=C2=A0 =C2=A0 =C2=A0 =C2=A0- packages need to be relocatable (not all a= re, e.g. the compiler)
=C2=A0 =C2=A0 =C2=A0 =C2=A0- there'll be a sm= all overlay (similar to opam-monorepo overlay) for a small set of packages = that are not possible to build with "dune pkg"
=C2=A0 =C2=A0 = =C2=A0 =C2=A0- timeline: first alpha was planned end of Q1, now scheduled f= or May
=C2=A0 =C2=A0 =C2=A0 =C2=A0- what needs to be done for mirage? we= haven't tested it yet. need to discuss and test once an alpha is aroun= d (thomas will test even earlier)
=C2=A0 =C2=A0 =C2=A0 =C2=A0- for now w= e need to keep opam-monorepo
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Thomas: are th= ere urgent pains to address?
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Hannes: hard t= o use old versions of dunes, ...
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Hannes: I= s there any specification of how dune pkg will download/organize etc., for = the purpose of reproducible builds? -- Thomas: it created a lock file and d= ownloads using opam-lib
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Hannes: carton/git = issue with opam-monorepo -- Thomas: this will be fixed in "dune pkg&qu= ot;
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Dune pkg milestone: https://github.com/ocaml/dune/issues?q=3Dis%3Aopen+is%= 3Aissue+milestone%3A%22Package+Management+MVP%22
=C2=A0 =C2=A0 =C2= =A0 =C2=A0- dune+orb (reproducible build integration): https://github.com/ocaml/dune/issues/9548=
=C2=A0 =C2=A0 - Performance considerations for MirageOS (let's = take mirage-crypto as example)
=C2=A0 =C2=A0 =C2=A0 =C2=A0- EC NIST curv= es pre-computed tables -- https://github.com/mirage/mirage-crypto/pull/191 shows a sp= eedup of 4x
=C2=A0 =C2=A0 =C2=A0 =C2=A0- mirage-crypto symmetric cipher = (AES-GCM / Poly1305-Chacha20) around 10x slower than OpenSSL (see https://github.com/mi= rage/mirage-crypto/pull/203, a speedup of ~2.5x for chacha using string= /bytes)
=C2=A0 =C2=A0 =C2=A0 =C2=A0- cstruct.t vs bytes -- https://blog.robur.= coop/articles/speeding-ec-string.html shows a speedup of 2.5x
=C2=A0= =C2=A0 =C2=A0 =C2=A0- or replace the underlying structure of cstruct from = bigarrays to bytes? "Just" have to take care of IO-pages which st= ill need aligned addresses
=C2=A0 =C2=A0 =C2=A0 =C2=A0- for Xen interfa= ces we need page-aligned non-moving memory areas
=C2=A0 =C2=A0 =C2=A0 = =C2=A0- Dinosaure: don't use _systematically_ Cstruct=E2=80=A7t and pro= bably we should use bytes more systematically and asking ourselves about pa= rticularities of bigarray
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Thomas: Patrick h= as started a Bstruct library: https://github.com/ocaml-multicore/ocaml-uring/pull/= 101
=C2=A0 =C2=A0 - mirage-flow + shutdown (https://github.com/mirage/mirage-flow/pul= l/48)
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Hannes: released to opam-reposito= ry as mirage-flow 4.x
=C2=A0 =C2=A0 =C2=A0 =C2=A0- Hannes: anyone eager = to review: http= s://github.com/mirage/mirage-tcpip/pull/512
=C2=A0 =C2=A0 =C2=A0 =C2= =A0- Thomas: will ping Dave
=C2=A0 =C2=A0 - Next meeting - https://meet.jit.si/mirageos-call, 9 C= ET in two weeks (March 11th)

### Moved to next meeting
- Unikraft= +mirage plans
- How can we improve the security story around MirageOS? W= hat are the security issues with mirage?
- What do we want Mirage5 to lo= ok like?
=C2=A0 =C2=A0 - Ocaml 5 support
=C2=A0 =C2=A0 - No more Lwt?=
- IncludeOS / Mirage

On Mon, Mar 11, 2024 at 9:09=E2=80=AFAM = Magnus Skjegstad <magnus@v0.no> w= rote:
Reminder, = the MirageOS meeting is starting in a few minutes.

Agenda: https://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA=
Meeting link: https://meet.jit.si/mirageos-call

See you there,
Magnus

On Thu, 7 Mar 2024, at 12:31, Magnus Skjegstad wrote:
> Hi everyone,
>
> The next MirageOS meeting will be Monday March 11th at 9:00-10:00 CET.=
>
> Everyone is welcome to attend this bi-weekly meeting. It's a good =
> opportunity to meet others working on MirageOS, discuss current or > future projects or PR review.
>
> The current agenda is here: https://pad.data.coop/w= GS4r8RyTKqQ73mcw7FrwA
>
> We have some items that carried over from last time, but feel free to =
> add any additional items you'd like to discuss.
>
> The Jitsi link for the meeting is https://meet.jit.si/mirageos= -call
>
> --
> Magnus



--
Romain Calasc= ibetta - http://din.osau.= re/
--0000000000006c5aa906136338b9-- From mirageos-devel-bounces@lists.xenproject.org Sat Mar 23 19:16:05 2024 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 23 Mar 2024 19:16:05 +0000 Received: from list by lists.xenproject.org with outflank-mailman.697340.1088400 (Exim 4.92) (envelope-from ) id 1ro6qP-0004hu-9t; Sat, 23 Mar 2024 19:15:53 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 697340.1088400; Sat, 23 Mar 2024 19:15:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1ro6qP-0004hn-79; Sat, 23 Mar 2024 19:15:53 +0000 Received: by outflank-mailman (input) for mailman id 697340; Sat, 23 Mar 2024 19:15:51 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1ro6qN-0004hh-Ad for mirageos-devel@lists.xenproject.org; Sat, 23 Mar 2024 19:15:51 +0000 Received: from fout1-smtp.messagingengine.com (fout1-smtp.messagingengine.com [103.168.172.144]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id c1edbf52-e949-11ee-afe2-a90da7624cb6; Sat, 23 Mar 2024 20:15:50 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfout.nyi.internal (Postfix) with ESMTP id DF07F1380093 for ; Sat, 23 Mar 2024 15:15:48 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute5.internal (MEProxy); Sat, 23 Mar 2024 15:15:48 -0400 Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9DA692A2008B; Sat, 23 Mar 2024 15:15:48 -0400 (EDT) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" X-Inumbo-ID: c1edbf52-e949-11ee-afe2-a90da7624cb6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=v0.no; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s= mesmtp; t=1711221348; x=1711307748; bh=0VXTyjMIFRUGdqSVcqRlhs2nj NERnrJWqrn5PS984d0=; b=QdOlozAwfiU01CUDoCjFmF+EsQerDMnUTgbTp1Mgw c4kOY3w714jANvJ3BvOSF37lsiM96KGg/1A1Mf+hNO0va7M4P0c9OLjUXBCzNkGe jWcV9vIHgKADK94gZC5Ki/y7xKhwCMWx2o+GjL6Il3debIfU2K9onhMqFJTVx8gY J8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1711221348; x=1711307748; bh=0VXTyjMIFRUGdqSVcqRlhs2njNERnrJWqrn 5PS984d0=; b=YROJdwRZ4mOP4ox+73dSfcIap7RsaBB8Sx7gR3uY0Gt0/2beyCr dGLVwn2wfICuBLDsMeb7s2+KmMquDYMIZHfr8lEe8wycp5RJ/LjxFpuvlHVopKWZ eC58pWjJRUPFzeEg/cydEbrg6b5EJDqKoKx0qYD/gBzvjrPx8n8PD5BvJGiqNDYU WUlnZMKucb6R1RZw7dwzgRI1b6CecCEIqYS8rPQNcKgDhKuqdSSriVIdRbb4K6DU goTb2XNNwRFjlLmTNkRXCtWxG2z2FON4LwoSsRQDzPCCrZPdZ5+dj9TmZwuSS/9a NxccRJ3jg2MexDChq8zqH//JAkWGJyT4eEQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledruddtgedguddvgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghgnhhushcuufhkjhgvghhsthgrugdfuceomhgrghhn uhhssehvtddrnhhoqeenucggtffrrghtthgvrhhnpeetveeuuedvueetiedtudeuhedvte ejudfhfeetvdejhedukedvuefgffdvjeejvdenucffohhmrghinhepuggrthgrrdgtohho phdpjhhithdrshhinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepmhgrghhnuhhssehvtddrnhho X-ME-Proxy: Feedback-ID: i11304080:Fastmail X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-332-gdeb4194079-fm-20240319.002-gdeb41940 MIME-Version: 1.0 Message-Id: <3bee503c-445a-4b8b-88b1-6421c17d489f@app.fastmail.com> Date: Sat, 23 Mar 2024 20:15:23 +0100 From: "Magnus Skjegstad" To: mirageos-devel@lists.xenproject.org Subject: MirageOS meeting 2024-03-25 Content-Type: text/plain Hi everyone, The next MirageOS community call will be Monday March 25th at 9:00-10:00 CET. As usual everyone is welcome to attend this bi-weekly meeting. The current agenda is here: https://pad.data.coop/wGS4r8RyTKqQ73mcw7FrwA Feel free to add any additional items you'd like to discuss. The Jitsi link for the meeting is https://meet.jit.si/mirageos-call See you there, Magnus