From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from kate-mail.whsl206.com ([49.50.249.113]) by ewsd; Tue Mar 10 19:50:48 EDT 2020 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=qs.co.nz; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:To:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2I1SzoQBL9MNNbh3ligpWj2cQvuMLINa0S1JS2O0kmw=; b=fnfQ04Ueug3bWovAy4kzS0cs/C L2By/0QfBYQL9cKtQBEHE12Pv3+f1QvyXUv5i0ci0TqfC4d5la5XzaAJY79ZfNP8cFwdW5n8PIT3K qLI0iqDsmQ0ufZyNQrej2HPHdGMvlI381VTvd+Fi1RdNf9cLOZKPJEw1AyIL+lRsa1jHql8fGFwuZ bZJ6LCJXMxKbWClSni1gbHtmFgoVsw7YfxkkC/1RHp4/jgDt8Zyfgb3PVRMd/WgjJdSr2SYc0CwU6 707DjWoak1eDVI+P1IUHI3jj2qHk9dlWZvSoFMLITm6YzZ9FWBMK8yHLDdcH4L8uzibIG9yGD3Eiq tYTddrhg==; Received: from [118.149.223.243] (port=1442 helo=[192.168.43.110]) by kate.whsl206.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1jBodL-00F07m-Kx for 9front@9front.org; Wed, 11 Mar 2020 12:49:59 +1300 To: 9front@9front.org From: Trevor Higgins Subject: How is smp handled in file services? Message-ID: Date: Wed, 11 Mar 2020 12:49:56 +1300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - kate.whsl206.com X-AntiAbuse: Original Domain - 9front.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - qs.co.nz X-Get-Message-Sender-Via: kate.whsl206.com: authenticated_id: phil@qs.co.nz X-Authenticated-Sender: kate.whsl206.com: phil@qs.co.nz X-Source: X-Source-Args: X-Source-Dir: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: AJAX STM-aware descriptor general-purpose layer Just trying ti understand the data flow through the kernel (as compared to *nix). Given the following easy to understand example: Assume that three processes are writing to /dev/audio through the mixfs file server. Given that all processes are on the same terminal server, and that there are ample idle cpu cores (ignore locking and other side effects), what is the data flow path in mixfs: 1. All three procs sleep while some proc processes the write requests sequentially, returning the results sequentially. 2. All three procs enter the file service and process one request concurrently and return result directly to own process. I am assuming that unless designed specifically in the file server, that the answer is 1. -- We need another plan