From nobody Sun Feb 20 00:26:24 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 60B2619CE8C3 for ; Sun, 20 Feb 2022 00:26:27 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K1R7Q20wcz4rj3 for ; Sun, 20 Feb 2022 00:26:26 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: by mail-qv1-xf2f.google.com with SMTP id f19so22675824qvb.6 for ; Sat, 19 Feb 2022 16:26:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=+y5IEz1wCIwHHYcg6W2qUDQAES+JlSU18ygcraiWno8=; b=ma2x46kqjwbI14J/Ze65EVASAMc0uzPbidt5m3F1iuseCGKw0J3GldLlTyjNBMxidk v6pZvrQkTUnOf5rjvrdtovonrRCDEs8RQ+5Vdc8bjXvkECpwa5LjGq8oMR8k+tBOwHqx rFMX6FUtoCTx+0uA95hc903RLdfkXTRyA4nCMcIwZS38mrd/+GFljS7L3UIMDFCoou/Y epLpTjpF0Ykds/UBvLDNNTEN84mI3QNwYExIRK/CxZGzhjKoLjmtCekw5Jpd/pt/I/r5 ZTD3CjM15EVqGBYAPUBxVnIyom6omUIGmd0xa8gZdQx/FiopB29B98ObKThlhQ49KGUH dYpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:message-id:date:mime-version:user-agent :subject:content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=+y5IEz1wCIwHHYcg6W2qUDQAES+JlSU18ygcraiWno8=; b=qVDjTMGQwgdx+sjKgVRgYDK2UzZ7wNoHwJYMGxzvDgmVL13Yjez3KrPnVdGs7elP5a 34Hil2tiZYHNPQLInXguzKh/HFttvIt0jBJkt8QhQq87LJjqzSJWKtw4H0lZvaZG1Pu1 nrPbZ1WfuoYus/FDlsoTSwK0VKVFdVAu90FsjpyMa2uKI7gzp+BPNf+dnYw2h/bUw7FN qPmf5KOdxj2arUqoBQ1MShn9AqpPAy2MI0r0XWh53VkEj0OI9Fq2Rbm0pw7+85yRvuD0 w+UnZSDC+GJnKMlA+aawGms2TbWYwzuzXfjfdMCZ9ExUYoKDLAxWiDEpst0/W9k7cl4m df+g== X-Gm-Message-State: AOAM531MMhRvdHPM98h6ArShssUKbv0UDntALT8RdWyCci8rmSIQccTh JF4kia5yKytE+kZUZOBKQL0= X-Google-Smtp-Source: ABdhPJznaGCRijWgo1fuoiLeOP43lA8VbwrrJjONTdF4BqTRDyl3j24xF+ZJ9rv5gKfIhK5JmT4cGQ== X-Received: by 2002:a05:622a:1a8d:b0:2de:6b8:e8ca with SMTP id s13-20020a05622a1a8d00b002de06b8e8camr840882qtc.373.1645316785694; Sat, 19 Feb 2022 16:26:25 -0800 (PST) Received: from [10.231.1.66] (075-130-069-034.biz.spectrum.com. [75.130.69.34]) by smtp.gmail.com with ESMTPSA id v14sm29008320qtk.5.2022.02.19.16.26.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 19 Feb 2022 16:26:25 -0800 (PST) Message-ID: <59cbcfe2-cd53-69d8-65d6-7a79e656f494@FreeBSD.org> Date: Sat, 19 Feb 2022 19:26:24 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: [Intel AlderLake] Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core Content-Language: en-US To: Konstantin Belousov Cc: Mike Karels , Tomoaki AOKI , "Chen, Alvin W" , freebsd-current@freebsd.org References: <5fd2a34e-1135-4237-a028-d4566ff65c69@FreeBSD.org> <20220219115534.7db1b9f199c10894e4280b33@dec.sakura.ne.jp> <7A743668-B5AA-4679-9F56-9A6220CBBC14@karels.net> From: Alexander Motin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4K1R7Q20wcz4rj3 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=ma2x46kq; dmarc=none; spf=pass (mx1.freebsd.org: domain of mavbsd@gmail.com designates 2607:f8b0:4864:20::f2f as permitted sender) smtp.mailfrom=mavbsd@gmail.com X-Spamd-Result: default: False [-3.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FORGED_SENDER(0.30)[mav@FreeBSD.org,mavbsd@gmail.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[mav@FreeBSD.org,mavbsd@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[FreeBSD.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f2f:from]; MLMMJ_DEST(0.00)[freebsd-current]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 19.02.2022 13:23, Konstantin Belousov wrote: > On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote: >> On 19.02.2022 12:02, Mike Karels wrote: >>> On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote: >>>> Just a thought, but can it be the reason with timing (e.g., rendezvous >>>> within (i)threads, hardware controlls without using hardware timer) >>>> problem? >>>> >>>> On FreeBSD, IIUC, multi processor (multi core) implementation assumes >>>> SMP (differs only clock speed) and end up with difference of >>>> performance at same clock speed within P-core and E-core, possibly. >>> >>> Another possibility is that the system is confused by having hyperthreading >>> on the P cores but not the E cores. >> >> No, I've tried to disable SMT and different number of cores to make it look >> identical and uniform for the scheduler. The only thing I could not test is >> disabling all P cores to test only E, the motherboard does not allow that, >> requiring at least one P core enabled. > > Does the kernel select MWAIT as the idle method? If you set idle to spin, > is anything change? By default kernel selects ACPI, using MWAIT: machdep.idle: acpi dev.cpu.0.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc I've tried to do in loader: set machdep.idle_mwait=0 set machdep.idle="spin" (also tried "hlt") , but without visible positive effects. -- Alexander Motin