Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp2734983ybh; Mon, 16 Mar 2020 08:43:05 -0700 (PDT) X-Google-Smtp-Source: ADFU+vuStyvtbJUbMhRIJDYg0lKAjS5QtWD9HAGHY5RVBa0d955te/qrpYknqtkApf621yaEzitB X-Received: by 2002:a9d:a68:: with SMTP id 95mr21890677otg.87.1584373385156; Mon, 16 Mar 2020 08:43:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584373385; cv=none; d=google.com; s=arc-20160816; b=ie5eNaaeHSlglBrmmyirYOcezy6yiOa6Xtlf3qum7MeSq2oMP++ar74V60RmUFsyX0 u0EQhKb9Yu0MysFGlLX/cdL2JiCfEyV91Hp4GQxnWZ+PE5+s0v2o8RiBZNNTcx0P/8Vh zSXSjRnrx9gibm/Mr9lUcP3319Q0BdaI3wJ1VVXPCnxpvWGbYcmJK4bI9aK9y5QxwyI6 UaDB8IV4boebiW8k2pTWbJuciw2W0axwx/EfoDG5NXddrQK6lQpse63qtirpwKp1ZUX7 0mz1Ow8uV92tHB30iMfx8M0qKRgZm/HG90l4HwJ1xNOBGaL3ZcNWku9wqfSRDboGuFMo sbZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:date:cc:to:from:subject:message-id; bh=qKrl1YIwfw99cKtKgzdAIRbrdDuRdXPMd96wpLBMSHY=; b=KxLtTvp2gF0ojYcWwgoJJ6G6QRuZ4uo4m+rsl0ZIufd7f6fSkuanJR7qjRUNu+bkpJ IY0Trpw6yMiczjoKvoGRCV3CCwLKub2RRoZuT3aTWmFZoFyRbaK34pc6ikBTRInRPdgo GLIqs1L9BIIUAHPSNT50RJfjrtlYcuQCSB94omvTJ4D3AHBtqPq0m2mLvYB2B+hFLzFd 9G3GLfNXHkKxJFLxElFr/5P2yAsWwIEL69VNV3NDJH1TMCdG6v4UHOhcWAgkNpwdhT5D ZYB8aO+I2v+b/HW1cR7O2WReTmRdHHzfheMq7tZzA/T8kCrEn0FKIJYinpIU6yUnrisE BjMQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q13si148660otn.141.2020.03.16.08.42.40; Mon, 16 Mar 2020 08:43:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731768AbgCPPmc (ORCPT + 99 others); Mon, 16 Mar 2020 11:42:32 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:37732 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731744AbgCPPmb (ORCPT ); Mon, 16 Mar 2020 11:42:31 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) (envelope-from ) id 1jDrsr-00GkBO-Nr; Mon, 16 Mar 2020 16:42:29 +0100 Message-ID: Subject: Re: Simulate Radio wave interference From: Johannes Berg To: Masashi Honma Cc: linux-wireless@vger.kernel.org Date: Mon, 16 Mar 2020 16:42:28 +0100 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi, It's a bit over three years ago you wrote this, so perhaps you won't really remember, but I'm not sure I can make sense of the code and wanted to ask if you can help out. In particular, I'm wondering about the timing aspects of this interference simulation. The commit message says: > In real space, there could be interference of radio waves. This commit > considers a radio wave which has signal strength under > CCA_THRESHOLD(-90) causes interference. This commit accumulates such > radio wave signal strength and decreases it from tx power. I don't see this - the signal strength is just taken as is, and overwritten, so there's no accumulation going on? And the timing is just odd - the duration of the interference is added to at the *end* of each transmission, and every 10 ms the duration of the interference is calculated into a probability? I'd have expected this to be something like have a list of signals, with * transmitter (location) * signal strength added to the list at the beginning and removed at the end. Or alternatively, perhaps easier to use, for each destination station the cumulative noise received at there from far away transmissions, already weighed by distance (though that's tricky since stations can move). Then, when actually "transmitting" the frame, check that value, or sum up all the lists by location/fading by distance. I guess my question really is how what's actually implemented is meant to map to the physical world? Thanks, johannes