From owner-freebsd-hackers@freebsd.org Mon Jan 28 08:24:26 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B340A14AB261 for ; Mon, 28 Jan 2019 08:24:26 +0000 (UTC) (envelope-from farrokhi@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2756D77B23; Mon, 28 Jan 2019 08:24:26 +0000 (UTC) (envelope-from farrokhi@FreeBSD.org) Received: from [192.168.202.173] (095-097-247-129.static.chello.nl [95.97.247.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: farrokhi) by smtp.freebsd.org (Postfix) with ESMTPSA id 8256D338F; Mon, 28 Jan 2019 08:24:25 +0000 (UTC) (envelope-from farrokhi@FreeBSD.org) From: "Babak Farrokhi" To: "Mark Saad" Cc: "FreeBSD Hackers" Subject: Re: CPU Isolation Date: Mon, 28 Jan 2019 09:24:20 +0100 X-Mailer: MailMate (1.12.4r5594) Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_B7D54A7F-232F-420C-88B2-E4C3D7C8F327_="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Rspamd-Queue-Id: 2756D77B23 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.88 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.995,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.88)[-0.882,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 08:24:27 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_B7D54A7F-232F-420C-88B2-E4C3D7C8F327_= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable AFAIK there is no way to do it pre-boot. To do the isolation post-boot yo= ur best bet is cpuset(1) (with which I could not totally isolate cpu core= s as dedicated application cores). On 22 Jan 2019, at 19:29, Mark Saad wrote: > All > I am looking to setup a 12-STABLE box in a way that is similar to a > CentOS server I am running. > That server is setup using the boot option isocpus, to remove > cores/cpus from the kernel scheduler at boot. What I want to try on > 12-STABLE is to set aside some cores to run process and some kernel > threads that will only always run on a dedicated core with out the > chance for being preempted / interrupted by something else on that > core / cpu . What I do not see is a way to evict processes off a > running cpu post boot or a way to isolate them preboot. Am I missing > something? > > -- = > mark saad | nonesuch@longcount.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" --=_MailMate_B7D54A7F-232F-420C-88B2-E4C3D7C8F327_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQKTBAEBCAB9FiEE8IFfiGG/LeryYenBayZ62F1jLpoFAlxOvDRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYw ODE1Rjg4NjFCRjJERUFGMjYxRTlDMTZCMjY3QUQ4NUQ2MzJFOUEACgkQayZ62F1j LpqkxhAAkKizxi6WNfxqTb4TztF9ospd99PtyYYnuLv0BgWXkFeJX5FDj4uLli3y ZYXjBpdo74cHWteNjufYtslUPktnDn0Ww9aNFSjbOn/3yFmkrBhOoJY3Y6BmKIUe BECNoJocuZCCmhgDCslNp6Gf3geEyF956NsEzlD1lF1+Ct8MRheq9rhMMBtCuleo 6031Xh5escWHudff3CU1sOYmhERMVfwLt9LvjYZXfuLCVPiSSAguSeDtbPqjspO6 ZeBSfeS1LsRJ5SdeIVwSpPte02w9/fO0/kave/gM6Ew02tNR2FQ7DaDFGkEzxyS/ uVQBCsOOJgqkMK+60qzhmFpy4MLWTpDNUniFLbTnKbkTQBvPH4j+osKp2Pzt3A84 8wZ2IyjdnUTTYz46zoJroGpCKfSpsV21VkmYPoJHoqd0ieEzk+upkjXYYWk3vEvT odwJKhC3AfMxf3DCnTlfWQruAdOjC7rvzYR/a3JvNmVpftXwcobd5mLsX07t8LRW 0m79RaL8AkXG5sYUzdzfzT8bBNXYKJSMxZWqtrvMW7azV0pguu5yiV1O6RqHL1Dq nWNo5Qo0HO3K4u+x+6gm/jusCyOYM3iGTkUycfL5XKsFCKqVYCyq+pPGGeT90RMX H+flHxW03f4ZpNNaW/IxDffjyK/VTDwD/utcYB35mJaV6viCkEQ= =k/A6 -----END PGP SIGNATURE----- --=_MailMate_B7D54A7F-232F-420C-88B2-E4C3D7C8F327_=-- From owner-freebsd-hackers@freebsd.org Mon Jan 28 08:34:36 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4DCB14AB730 for ; Mon, 28 Jan 2019 08:34:35 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id D29CD80190; Mon, 28 Jan 2019 08:34:34 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id F3619202561D; Mon, 28 Jan 2019 08:34:33 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id x0S8YXsE064101 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 28 Jan 2019 08:34:33 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id x0S8YXdZ064100; Mon, 28 Jan 2019 08:34:33 GMT (envelope-from phk) To: "Babak Farrokhi" cc: "Mark Saad" , FreeBSD Hackers Subject: Re: CPU Isolation In-reply-to: From: "Poul-Henning Kamp" References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <64098.1548664473.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Jan 2019 08:34:33 +0000 Message-ID: <64099.1548664473@critter.freebsd.dk> X-Rspamd-Queue-Id: D29CD80190 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.69 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.82)[0.824,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.dk]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.72)[0.716,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: phk.freebsd.dk]; NEURAL_SPAM_LONG(0.78)[0.784,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; RCVD_NO_TLS_LAST(0.10)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; IP_SCORE(0.07)[asn: 1835(0.37), country: EU(-0.00)] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 08:34:36 -0000 -------- In message , "Babak Farr= okhi" writes: >AFAIK there is no way to do it pre-boot. To do the isolation post-boot yo= ur >best bet is cpuset(1) (with which I could not totally isolate cpu cores >as dedicated application cores). The trick is to move /sbin/init to /sbin/init.real and create a /sbin/init shell script which cpuset's PID=3D1 then exec's /sbin/init.real Be aware that the surroundings of that shell script are very sparse. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-hackers@freebsd.org Mon Jan 28 11:37:49 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7EC514B0318 for ; Mon, 28 Jan 2019 11:37:49 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7307387224; Mon, 28 Jan 2019 11:37:47 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 9CF1E20964; Mon, 28 Jan 2019 06:37:46 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 28 Jan 2019 06:37:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=borderworlds.dk; h=subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=b nhkFbbVCIP4jgNCjMpdOl8Ef2YDeZC0R5HIeJnHNwA=; b=whqGspxhbTTwcGjbo Z6HRrd3AKiqXbLxRxLpBaxHaYG65tIKdkqu3N+/Sdz6He/bgEmn0OS4NfVPQzOYj x5QpwyeuxZio9rNJehoQ2aV4DgzJlnvSRg+LErq9WyZsIusoeDk5AItpN1sNhJR2 uc37yQxfHTxQ6KIT8t6x2lttN1VFDsRf2GS6oUhzuAPaLT57wqxZxyZ8C2CbXjiE 8AAFm9fBPGfz6aydBKgnrZzJQznKp9ZkrMzWJE2SmeQ5Wdm98dtsit74sdYfUWyw 0jP6a3XOsv2VMy1Ms3EpxY76hAo8q8c2YAiwJNiFYa9Am7JTYcolQZJRs1z2Qh/C 3Ns9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=bnhkFbbVCIP4jgNCjMpdOl8Ef2YDeZC0R5HIeJnHN wA=; b=QKKBnt7gDibV6/RcbKZ7BmPeIUG8DmxX/b0f68w0eLo2jh66UY8BH2/JM 6LJuTDB3EcGj8qj3/JXGMfN7p2+9jELOiLZjVsyn5a4K4t/Zfg8CCpK/7c0X8Ixi h+hPohN5eBXAuHWYyG+s/QSXPL+duN+aUG9blxMyJWTNCZP5tdVjERInW70bsg1s A4txX6J29KqloVyJGuh98vnpw7U9PfgWDdS95mQAWT8Qgxu2DdBP7dHiHEz8s6WQ 5PReQvs0LPZgwAIidYikAZu2Pzx3ZZkvypnX1bWybjADZYJBvuVN8tjiCZR5vON9 /CenOvgqVCqhmsFOgHdtaV7cbTefA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjedtgdeffecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhohfkff gfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpeevhhhrihhsthhirghnpgfuthoorhhk uceogihisegsohhruggvrhifohhrlhgushdrughkqeenucfkphepkeehrdduledurdduvd dvrddvuddtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeigihessghorhguvghrfihorhhl ughsrdgukhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from borg.borderworlds.dk (unknown [85.191.122.210]) by mail.messagingengine.com (Postfix) with ESMTPA id 3FBEF100BB; Mon, 28 Jan 2019 06:37:45 -0500 (EST) Subject: Re: CPU Isolation To: Poul-Henning Kamp , Babak Farrokhi Cc: FreeBSD Hackers , Mark Saad References: <64099.1548664473@critter.freebsd.dk> From: =?UTF-8?Q?Christian_St=c3=a6rk?= Organization: The Border Worlds Message-ID: <011a4a81-1cca-d97e-a355-9f2e8ff8b5c6@borderworlds.dk> Date: Mon, 28 Jan 2019 12:37:44 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <64099.1548664473@critter.freebsd.dk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: da X-Rspamd-Queue-Id: 7307387224 X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=borderworlds.dk header.s=fm1 header.b=whqGspxh; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=QKKBnt7g; spf=pass (mx1.freebsd.org: domain of xi@borderworlds.dk designates 66.111.4.29 as permitted sender) smtp.mailfrom=xi@borderworlds.dk X-Spamd-Result: default: False [-7.01 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[borderworlds.dk:s=fm1,messagingengine.com:s=fm1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[borderworlds.dk]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[borderworlds.dk:+,messagingengine.com:+]; MX_GOOD(-0.01)[in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com,in2-smtp.messagingengine.com,in1-smtp.messagingengine.com]; NEURAL_HAM_SHORT(-0.77)[-0.774,0]; IP_SCORE(-3.63)[ip: (-9.71), ipnet: 66.111.4.0/24(-4.70), asn: 11403(-3.64), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[29.4.111.66.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 11:37:50 -0000 On 1/28/19 9:34 AM, Poul-Henning Kamp wrote: > -------- > In message , "Babak Farrokhi" writes: > >> AFAIK there is no way to do it pre-boot. To do the isolation post-boot your >> best bet is cpuset(1) (with which I could not totally isolate cpu cores >> as dedicated application cores). > The trick is to move /sbin/init to /sbin/init.real and create a > /sbin/init shell script which cpuset's PID=1 then exec's /sbin/init.real > > Be aware that the surroundings of that shell script are very sparse. > Or maybe set "init_path" in loader.conf to point to the init wrapper and then keep /sbin/init unchanged. Then subsequent system updates would not break the setup. Best regards Christian From owner-freebsd-hackers@freebsd.org Mon Jan 28 12:20:16 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 637A714B1E48 for ; Mon, 28 Jan 2019 12:20:16 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward105o.mail.yandex.net (forward105o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::608]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E69C388F97 for ; Mon, 28 Jan 2019 12:20:14 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback13o.mail.yandex.net (mxback13o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::64]) by forward105o.mail.yandex.net (Yandex) with ESMTP id 18EF142022F6; Mon, 28 Jan 2019 15:20:04 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback13o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id N3UAKkgpGX-K3guLog5; Mon, 28 Jan 2019 15:20:04 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1548678004; bh=DxxuSo0LUR7irQatXzGWAilg66p87UksFIiStA7F0rc=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=ayEvjbvoCjz684Vml0dalL9b21d6kPMj+qrku9PkczUiIOexFV3t7uaYXk4AEwQ0H iP+Ks/XT7nTpZfn3va96WtpvheyMqSQwEz2DUAuPAFvt+mVSWyfNuwPG5rYFRVsreA 3aNK8xBygJzDDKFfjK/kCbdxYrzWrw11fCAlUSzI= Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id T4F4aXYyoG-K3kmkLe6; Mon, 28 Jan 2019 15:20:03 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Subject: Re: CPU Isolation To: Mark Saad , FreeBSD Hackers References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Autocrypt: addr=bu7cher@yandex.ru; prefer-encrypt=mutual; keydata= mQENBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYbxNk7qUC5 21YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ijZEjWHV91hY1YTHEF ZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7QEiWpyLVwECgLX2eOAXByT8B bCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDBVDGiOgvfxqidab7fdkh893IBCXa82H9N CNwnEtcgzh+BSKK5BgvPohFMgRwjti37TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEB AAG0JUFuZHJleSBWLiBFbHN1a292IDxidTdjaGVyQHlhbmRleC5ydT6JATgEEwECACIFAkwB F1kCGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEAHF6gQQyKF6qmYIAI6ekfm1VA4T vqankI1ISE6ku4jV7UlpIQlEbE7/8n3Zd6teJ+pGOQhN5qk8QE7utdPdbktAzi+x7LIJVzUw 4TywZLXGrkP7VKYkfg6oyCGyzITghefQeJtr2TN4hYCkzPWpylkue8MtmqfZv/6royqwTbN+ +E09FQNvTgRUYJYTeQ1qOsxNRycwvw3dr2rOfuxShbzaHBB1pBIjGrMg8fC5pd65ACH5zuFV A0CoTNGMDrEZSfBkTW604UUHFFXeCoC3dwDZRKOWJ3GmMXns65Ai5YkA63BSHEE1Qle3VBhd cG1w0CB5FBV3pB27UVnf0jEbysrDqW4qN7XMRFSWNAy5AQ0ETAEXWQEIAJ2p6l9LBoqdH/0J PEFDY2t2gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+ LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cvoYxj3dz4 S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQravXpZkl5JG4eOqJVIU X316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhYkPKVn7z1sZiB7W2H2TojbmcK HZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUAEQEAAYkBHwQYAQIACQUCTAEXWQIbDAAK CRABxeoEEMihegkYCAC3ivGYNe2taNm/4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw 98OmX7G0OV9snxMW+6cyNqBrVFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQ WfyJJIM7l3gv5ZS3DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLoz BcFCNdDAyXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85JJrV1mi5i Message-ID: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> Date: Mon, 28 Jan 2019 15:16:49 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="n1dsZjHoErZsGcMnWjuLjoEBRHUEQgIBG" X-Rspamd-Queue-Id: E69C388F97 X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yandex.ru header.s=mail header.b=ayEvjbvo; dmarc=pass (policy=none) header.from=yandex.ru; spf=pass (mx1.freebsd.org: domain of bu7cher@yandex.ru designates 2a02:6b8:0:1a2d::608 as permitted sender) smtp.mailfrom=bu7cher@yandex.ru X-Spamd-Result: default: False [-7.92 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1a2d::/64]; FREEMAIL_FROM(0.00)[yandex.ru]; HAS_ATTACHMENT(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yandex.ru:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yandex.ru,none]; MX_GOOD(-0.01)[mx.yandex.ru,mx.yandex.ru,mx.yandex.ru,mx.yandex.ru,mx.yandex.ru]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; RCVD_IN_DNSWL_LOW(-0.10)[8.0.6.0.0.0.0.0.0.0.0.0.0.0.0.0.d.2.a.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; FREEMAIL_ENVFROM(0.00)[yandex.ru]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yandex.ru.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[yandex.ru:s=mail]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; IP_SCORE(-1.73)[ipnet: 2a02:6b8::/32(-4.81), asn: 13238(-3.84), country: RU(0.00)]; TO_MATCH_ENVRCPT_SOME(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 12:20:16 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --n1dsZjHoErZsGcMnWjuLjoEBRHUEQgIBG Content-Type: multipart/mixed; boundary="F2gXP0dA6UoPVGIH3Uk1bFYMwwWbkACYw"; protected-headers="v1" From: "Andrey V. Elsukov" To: Mark Saad , FreeBSD Hackers Message-ID: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> Subject: Re: CPU Isolation References: In-Reply-To: --F2gXP0dA6UoPVGIH3Uk1bFYMwwWbkACYw Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 22.01.2019 21:29, Mark Saad wrote: > All > I am looking to setup a 12-STABLE box in a way that is similar to a > CentOS server I am running. > That server is setup using the boot option isocpus, to remove > cores/cpus from the kernel scheduler at boot. What I want to try on > 12-STABLE is to set aside some cores to run process and some kernel > threads that will only always run on a dedicated core with out the > chance for being preempted / interrupted by something else on that > core / cpu . What I do not see is a way to evict processes off a > running cpu post boot or a way to isolate them preboot. Am I missing > something? >=20 After r331723 it is possible to make such separation after boot using cpuset(8). If you need this a bit early, you need to modify sbin/init. --=20 WBR, Andrey V. Elsukov --F2gXP0dA6UoPVGIH3Uk1bFYMwwWbkACYw-- --n1dsZjHoErZsGcMnWjuLjoEBRHUEQgIBG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlxO8rUACgkQAcXqBBDI oXrUmwf+PNpNxaqaxlfS3Xv02p+TimpKZIAUes9qcbovqsvwD9u9WWLF6AoDdbZJ iH5OmIHAQ+8iGvsZdqvW24pvnVRL0m+aTiQHO+6MSS3UnIXL0l91SuJLpWT5Y5D5 UvVVgo6duYR4tPuR7fW7AtVSE+AI7hZOElxOdNUpx1ZBmwc7TijQUBxoLTbx4rjh ANxueth/hOBTYPzShOyOOHJCPwDEfzbDmGHnrxh+3AZ17dvC3Daz2vhX85l9Zbr5 +z/zFS/EIHhacoK+g2PNxpOWm0SZoPpCGY09vKjibMZ9qlo1M8g3yeCtXzpOpWK6 Y1RObnfpCIhUJhladTfpWwnvajSLkg== =INDL -----END PGP SIGNATURE----- --n1dsZjHoErZsGcMnWjuLjoEBRHUEQgIBG-- From owner-freebsd-hackers@freebsd.org Mon Jan 28 18:15:40 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A63C214BAE67; Mon, 28 Jan 2019 18:15:40 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B1ACE70E54; Mon, 28 Jan 2019 18:15:39 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wr1-x442.google.com with SMTP id l9so19104340wrt.13; Mon, 28 Jan 2019 10:15:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=LISVyrTvtCvIBfaTEbL4j//rYYfEHTysIfN8DCXgr9A=; b=FwtdMr2oyR1Gk09kI2wGHysdi0PfypXSVWckNRxTnh2iZd9pap7/BuOGqIR+5fYls8 sjMvSuG6mqrLlUV8XfEtp9hziZ8NooFUJfZwB1N0N7c8MLqL7fmOvzq22G4BNWMWLtXG 5M90t8bEa0Qtl/kaBnuWfpMjfjDJDn2Vr+0x8XAmRDE7iojGVwpeNC8p1o3SqixD3RL9 89r+P8j25BjKvtNf7z+VcBHWhtTnPx/44vSFNKhRAtu9lzGipIqnI35IXbfPVVe2E4+a WrEH8r2vcnfyWDufXiz7ucu1NE42FaCkVPmFXciBWi9Hec9erPsbuLrP8Pd1ryFAWxyl Y20g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=LISVyrTvtCvIBfaTEbL4j//rYYfEHTysIfN8DCXgr9A=; b=pZblC7k+E8Yb9uB9RU3i/Xp1PqBJneRrLYqCYCKJveHNKMWlTxQf8kK5BnYqcjkKDw 41N+bVRxDihP2UuMYQc/TsnF9cFnuYxhX60OqCPNbaaGsvrYfB/cYRUMX6Ut+cuwjHb3 rj9hZV4LQKceT/3EykBLurhzClLc4uq25fyLQg7MSRJotMXZOjLv4a+7umtqHlav062F YJ7RSIRFOf2ULwwFOzFA+52YoxDs4tX+TK+5uhcUvSYx7U4zVg9VXWXXK3pUgf5kSf5N 86kJeVCpwOA3Iwn8X323Ttm64+e3uDr6kaA8QNTpEbFgu83cP8elSDBtg3MU2kEejiTF VCaA== X-Gm-Message-State: AJcUukcUkUUtCctglawPxsuyjP0jJu6KbWaz9KQZ9vQwP1/AIP3eD/sl a0zI1L6KfoR1+n2yBcmxZPjVn7AYlbcfUyepOZUhbqF3MeY= X-Google-Smtp-Source: ALg8bN4GsQxdJ1po27drFBOmL4/qCZCFUPH2cW1ErYCXfW3HFQG4BEXCRBEpIeyVxjuicAUCMNyHhtEmQDZO2VP2v68= X-Received: by 2002:adf:ff09:: with SMTP id k9mr21782198wrr.97.1548699338013; Mon, 28 Jan 2019 10:15:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Rajesh Kumar Date: Mon, 28 Jan 2019 23:45:26 +0530 Message-ID: Subject: Re: Enabling a ACPI eMMC device is causing kernel reboots with FreeBSD 11.2 To: freebsd-amd64@freebsd.org, freebsd-acpi@freebsd.org, FreeBSD Hackers X-Rspamd-Queue-Id: B1ACE70E54 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=FwtdMr2o; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rajfbsd@gmail.com designates 2a00:1450:4864:20::442 as permitted sender) smtp.mailfrom=rajfbsd@gmail.com X-Spamd-Result: default: False [-4.12 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; IP_SCORE(-0.53)[ip: (1.58), ipnet: 2a00:1450::/32(-2.25), asn: 15169(-1.92), country: US(-0.08)]; NEURAL_HAM_SHORT(-0.58)[-0.583,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 18:15:40 -0000 Hi, I tried my luck with the FreeBSD 12.0 as well as the -CURRENT branch as of date. I am still seeing the issue. Looks like, I missed the earlier response from Kib (in link below) to this thread (may be landed in my spam). Is there anything else I could try debugging here? http://freebsd.1045724.x6.nabble.com/Enabling-a-ACPI-eMMC-device-is-causing-kernel-reboots-with-FreeBSD-11-2-td6293375.html Thanks, Rajesh. On Fri, Nov 16, 2018 at 10:45 AM Rajesh Kumar wrote: > Hi, > > I did some study on this. During acpi_attach, if MCFG table is present, > FreeBSD tries to use it (That is to map the PCI Base address to virtual > address space). Setting hw.pci.mcfg=0, disables that mapping and lets the > system use the type 1 config access (which is IO port based access). So, > this is what hw.pci.mcfg does. > > In our case, we are enabling a device on the ACPI bus and made sure no > other ACPI device collides with the address range for PCI (which mcfg > says). So, why enabling a device on ACPI, is causing the memory mapped PCI > access go bad to panic/reboot the kernel? I tried to collect more info > enabling INVARIANTS, but in that case kernel panics much before in the boot > process. So, how could I proceed in debugging this issue? Any suggestions? > > > On Thu, Nov 8, 2018 at 4:14 PM Rajesh Kumar wrote: > >> Hi, >> >> I have amd64 board, which has a eMMC device on the ACPI bus. When I try >> booting FreeBSD 11.2 on this board, with eMMC device disabled in BIOS, it >> boots without any issues. But, when eMMC device is enabled in BIOS, >> FreeBSD 11.2 continuously reboots. >> >> When I have the following tunable set, FreeBSD 11.2 boots without any >> issues with eMMC enabled. >> hw.pci.mcfg=0 >> >> Observations : >> a) We have verified the ACPI device addresses (from DSDT table) doesn't >> conflict with the PCI address base (configured in MCFG table). >> b) The PCI address base from MCFG table is read correctly by kernel >> (Verbose boot prints that address). So, I don't think MCFG table pointer is >> corrupted and getting read properly. >> >> Questions : >> a) What does hw.pci.mcfg=0 actually do to get the reboot issue resolved? >> b) Why enabling a device on ACPI bus needs hw.pci.mcfg (PCI specific) to >> boot? >> >> Looks like the system reboots when the ACPI and PCI devices enumeration >> starts during the boot. So, seems ACPI (or) PCI devices aren't getting >> enough resources and so reboots. >> >> Thanks, >> Rajesh. >> > From owner-freebsd-hackers@freebsd.org Mon Jan 28 19:25:22 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2CE314BCB66 for ; Mon, 28 Jan 2019 19:25:22 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-ed1-x543.google.com (mail-ed1-x543.google.com [IPv6:2a00:1450:4864:20::543]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EBD674297 for ; Mon, 28 Jan 2019 19:25:21 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-ed1-x543.google.com with SMTP id f9so13987968eds.10 for ; Mon, 28 Jan 2019 11:25:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1Poj7Exj+acblKqgUccbF/ihSWkn7r9uVtsN4m/jj6o=; b=BLauJtP4pVn2q4+5I0GQyzge3FerYGBHYE8WtPNMxumHMgb4O9FPlqcLZtj2Z3zOvf 3Zq9aINr8xD8drwZOQtLeQUjcW9IU5/YgiS3p2TKxpJ9E8+y0AsmRj5tZ/+2HZjS2b7x YTHeLE5alQrt/FuW63BEbT4sbV6HpnXuiroCKayVTEFIBkIhe+iriuZDcrGJlYyMIi35 LE3guQZkuIjxAMXQHCSYTfpD4n01xIdZcN41mWixwf3cDv8QSyH7IGW3dSX/pXB967MI skAr5EnhC+GMbO1ZtHM4e+w2gq8yf6d0cvNDZit3j83Xz5REYq/onfGr12+Zk7A/19tM IvKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1Poj7Exj+acblKqgUccbF/ihSWkn7r9uVtsN4m/jj6o=; b=mzspQn3mxuDbWEAM8nxNkz8hzwmq909cjd/nKPXWZtvy7il6FwlWVCG+bqbDPAKxYZ A7nWN7NS30VXFqSRVfJHNJzWZQhfrd81lbp51amOi5/G2viuH+ACt6NiiJR8KbAygRua zzCkF1xDxuEuFmZ6kecddGwL7TpWgkDLaZ7w7iIXVp/FELTKXRQnsVslQ9gch7d9KAi6 gp6HcFz8GlL/QgjwrTsNFjC+lxIRw3JCgFB3vtrnG1GsljNvidvAcCQcJB3XmZ1KQGYy PBgPqrz/xOrhlm5bpUm142xCyGA64ZpYTZTJiXhyZtPJij8NrMye9EMCzwpQIfD2inYo +DFw== X-Gm-Message-State: AJcUukfEUmnTcj2in7gFYwkQOEMCDVrFKOeQ1eEwVg5WX1fudvREncfp nx46rFFyVq0HPRaOJO0B5PN2B9YA1F5xLdcaILHFcw== X-Google-Smtp-Source: ALg8bN7/h6ySGoPu2GtN8iXNm29yzoN02IL8nujzRWzkPrKpjZ7MAyotFAXwCnhr+JqK9829SsXwNwJ+T+qjx7Kk/kw= X-Received: by 2002:a50:b8e5:: with SMTP id l92mr22231603ede.294.1548703520355; Mon, 28 Jan 2019 11:25:20 -0800 (PST) MIME-Version: 1.0 References: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> In-Reply-To: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> From: Mark Saad Date: Mon, 28 Jan 2019 14:25:08 -0500 Message-ID: Subject: Re: CPU Isolation To: "Andrey V. Elsukov" Cc: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 8EBD674297 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=longcount-org.20150623.gappssmtp.com header.s=20150623 header.b=BLauJtP4 X-Spamd-Result: default: False [-3.20 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994,0]; R_DKIM_ALLOW(-0.20)[longcount-org.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.09)[-0.086,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[longcount.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt1.aspmx.l.google.com]; DKIM_TRACE(0.00)[longcount-org.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[yandex.ru]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.81)[ip: (0.21), ipnet: 2a00:1450::/32(-2.25), asn: 15169(-1.93), country: US(-0.08)] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 19:25:22 -0000 All Thanks for the replies, I had experimented with the init script method but ; I kept thinking that I was doing this wrong. I think that adding a loader option to isolate cpus from the scheduler would be useful; but I have no idea how to get there. My current plans are to setup init to use cpus 0-4 and to use 5-7 for my applications and see how it goes. The other test I want to try is to run some kernel threads on dedicated cores. Let me try to break stuff now. On Mon, Jan 28, 2019 at 7:20 AM Andrey V. Elsukov wrote: > > On 22.01.2019 21:29, Mark Saad wrote: > > All > > I am looking to setup a 12-STABLE box in a way that is similar to a > > CentOS server I am running. > > That server is setup using the boot option isocpus, to remove > > cores/cpus from the kernel scheduler at boot. What I want to try on > > 12-STABLE is to set aside some cores to run process and some kernel > > threads that will only always run on a dedicated core with out the > > chance for being preempted / interrupted by something else on that > > core / cpu . What I do not see is a way to evict processes off a > > running cpu post boot or a way to isolate them preboot. Am I missing > > something? > > > > After r331723 it is possible to make such separation after boot using > cpuset(8). If you need this a bit early, you need to modify sbin/init. > > -- > WBR, Andrey V. Elsukov > -- mark saad | nonesuch@longcount.org From owner-freebsd-hackers@freebsd.org Mon Jan 28 21:05:00 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25AB514BF9CD for ; Mon, 28 Jan 2019 21:05:00 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward100o.mail.yandex.net (forward100o.mail.yandex.net [37.140.190.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 190E877EEF for ; Mon, 28 Jan 2019 21:04:58 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback3j.mail.yandex.net (mxback3j.mail.yandex.net [IPv6:2a02:6b8:0:1619::10c]) by forward100o.mail.yandex.net (Yandex) with ESMTP id 9BD074AC1825; Tue, 29 Jan 2019 00:04:50 +0300 (MSK) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [2a02:6b8:0:1a2d::28]) by mxback3j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 6wKU6hPoJn-4owiJHYA; Tue, 29 Jan 2019 00:04:50 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1548709490; bh=vSNMcMcDv6lkb+MZH+V27sRXhEkAJr65jQfgzT6w13U=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=rOWlf66aDqX0L5h0HH7rrpf2mf3BXrKClgXr/9rKmrt6sCYKZChCkF4CaY7X3hXl9 hhR3mGhvt6YoOOxVDizmulR1mSbo079tUMid99hIqh6e8uDwND3gw7tRn0Bins2JNI r896V+klwPsvZsc0EZzAnxkrA9XaqgrBuDU2o8tU= Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id xTcjedm24o-4nnK2sDF; Tue, 29 Jan 2019 00:04:49 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Subject: Re: CPU Isolation To: Mark Saad Cc: FreeBSD Hackers References: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Autocrypt: addr=bu7cher@yandex.ru; prefer-encrypt=mutual; keydata= mQENBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYbxNk7qUC5 21YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ijZEjWHV91hY1YTHEF ZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7QEiWpyLVwECgLX2eOAXByT8B bCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDBVDGiOgvfxqidab7fdkh893IBCXa82H9N CNwnEtcgzh+BSKK5BgvPohFMgRwjti37TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEB AAG0JUFuZHJleSBWLiBFbHN1a292IDxidTdjaGVyQHlhbmRleC5ydT6JATgEEwECACIFAkwB F1kCGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEAHF6gQQyKF6qmYIAI6ekfm1VA4T vqankI1ISE6ku4jV7UlpIQlEbE7/8n3Zd6teJ+pGOQhN5qk8QE7utdPdbktAzi+x7LIJVzUw 4TywZLXGrkP7VKYkfg6oyCGyzITghefQeJtr2TN4hYCkzPWpylkue8MtmqfZv/6royqwTbN+ +E09FQNvTgRUYJYTeQ1qOsxNRycwvw3dr2rOfuxShbzaHBB1pBIjGrMg8fC5pd65ACH5zuFV A0CoTNGMDrEZSfBkTW604UUHFFXeCoC3dwDZRKOWJ3GmMXns65Ai5YkA63BSHEE1Qle3VBhd cG1w0CB5FBV3pB27UVnf0jEbysrDqW4qN7XMRFSWNAy5AQ0ETAEXWQEIAJ2p6l9LBoqdH/0J PEFDY2t2gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+ LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cvoYxj3dz4 S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQravXpZkl5JG4eOqJVIU X316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhYkPKVn7z1sZiB7W2H2TojbmcK HZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUAEQEAAYkBHwQYAQIACQUCTAEXWQIbDAAK CRABxeoEEMihegkYCAC3ivGYNe2taNm/4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw 98OmX7G0OV9snxMW+6cyNqBrVFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQ WfyJJIM7l3gv5ZS3DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLoz BcFCNdDAyXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85JJrV1mi5i Message-ID: Date: Tue, 29 Jan 2019 00:01:38 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0gOaGfzy4uR0QCkjOcUTlO6hoGKwlijVN" X-Rspamd-Queue-Id: 190E877EEF X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yandex.ru header.s=mail header.b=rOWlf66a; dmarc=pass (policy=none) header.from=yandex.ru; spf=pass (mx1.freebsd.org: domain of bu7cher@yandex.ru designates 37.140.190.180 as permitted sender) smtp.mailfrom=bu7cher@yandex.ru X-Spamd-Result: default: False [-6.96 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[yandex.ru]; R_SPF_ALLOW(-0.20)[+ip4:37.140.128.0/18]; HAS_ATTACHMENT(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yandex.ru:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yandex.ru,none]; MX_GOOD(-0.01)[cached: mx.yandex.ru]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.982,0]; RCVD_IN_DNSWL_LOW(-0.10)[180.190.140.37.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; FREEMAIL_ENVFROM(0.00)[yandex.ru]; ASN(0.00)[asn:13238, ipnet:37.140.128.0/18, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yandex.ru.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[yandex.ru:s=mail]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-0.77)[asn: 13238(-3.84), country: RU(0.00)] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 21:05:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0gOaGfzy4uR0QCkjOcUTlO6hoGKwlijVN Content-Type: multipart/mixed; boundary="1Vc4IEhZovUVfTQtXqpfaonPHZTy0goIz"; protected-headers="v1" From: "Andrey V. Elsukov" To: Mark Saad Cc: FreeBSD Hackers Message-ID: Subject: Re: CPU Isolation References: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> In-Reply-To: --1Vc4IEhZovUVfTQtXqpfaonPHZTy0goIz Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 28.01.2019 22:25, Mark Saad wrote: > All > Thanks for the replies, I had experimented with the init script > method but ; I kept thinking that I was doing this wrong. I think that > adding a loader option to > isolate cpus from the scheduler would be useful; but I have no idea > how to get there. My current plans are to setup init to use cpus 0-4 > and to use 5-7 for my applications > and see how it goes. The other test I want to try is to run some > kernel threads on dedicated cores. Let me try to break stuff now. As r331723 says, now kernel threads belong to cpuset #2, all other processes belong to cpuset 1. So, you can try to use commands: Limit all userlevel application to use only CPU cores 0-4: # cpuset -s 1 -l 0-4 Limit kernel level threads to use CPU only CPU cores 0-4: # cpuset -s 2 -l 0-4 and then dedicate CPUs 5-7 for your application with pid PID # cpuset -l 5-7 -p PID --=20 WBR, Andrey V. Elsukov --1Vc4IEhZovUVfTQtXqpfaonPHZTy0goIz-- --0gOaGfzy4uR0QCkjOcUTlO6hoGKwlijVN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlxPbbIACgkQAcXqBBDI oXqM3Af+JVauRTNAb1zdf8msElT5R40HUAslbM3/RTIrS9bzLL1K3yRy/72rSXOY LSLtWRTOWQQqkQ2qd2NxdFbiIzGINAuCJ8GJO+SKARRIsabWPOsXWw1z9mVl5hdi 5VbumtDHs+T3LqzRr2024KUF3GV+yNeSjUEW9Yp8H9JU9xWuOuicOcNMGH33OS/S +52Az2l+s062kKcZwrypI9X+qg5PyX380C5A/0iO/vcHOfQshD98hRe+bjWpDuiJ sNyJXucXtyIs37WRe8xmyK7gec4/LZ8ivWpHxmdJcHu2Dy33EardlgNBOfJLVTQ4 cVUfbAfl5pp6PaxgQKGrhrwl19Wqxw== =PqgO -----END PGP SIGNATURE----- --0gOaGfzy4uR0QCkjOcUTlO6hoGKwlijVN-- From owner-freebsd-hackers@freebsd.org Mon Jan 28 21:11:20 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C6A814BFC8F for ; Mon, 28 Jan 2019 21:11:20 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward105p.mail.yandex.net (forward105p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0E98E80130 for ; Mon, 28 Jan 2019 21:11:18 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback7j.mail.yandex.net (mxback7j.mail.yandex.net [IPv6:2a02:6b8:0:1619::110]) by forward105p.mail.yandex.net (Yandex) with ESMTP id D14F14D42457; Tue, 29 Jan 2019 00:11:07 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback7j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 7kh5O63FKD-B7GSwmIh; Tue, 29 Jan 2019 00:11:07 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1548709867; bh=6FbfqxLft4XujZB/5taNshv1QnSgyvvV68ewS61MzbU=; h=Subject:From:To:Cc:References:Message-ID:Date:In-Reply-To; b=SanRwLMaac6JrNkReUoiC9EfgelPXrE6PQm3itE2QDjeyHbZFC1oRNT6IYOpbqtz5 hUq/QoS85QWmyFcO/dO8KDdRpUFutDY9PQoMzIEHJMcId5umet8MHn2ABD8mHsR3bV Uj5AIsy1lUnls3M9K75vKHLWPM5lBp/NseM/IlQg= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ASAjCIoA5O-B7am8tmx; Tue, 29 Jan 2019 00:11:07 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Subject: Re: CPU Isolation From: "Andrey V. Elsukov" To: Mark Saad Cc: FreeBSD Hackers References: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Autocrypt: addr=bu7cher@yandex.ru; prefer-encrypt=mutual; keydata= mQENBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYbxNk7qUC5 21YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ijZEjWHV91hY1YTHEF ZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7QEiWpyLVwECgLX2eOAXByT8B bCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDBVDGiOgvfxqidab7fdkh893IBCXa82H9N CNwnEtcgzh+BSKK5BgvPohFMgRwjti37TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEB AAG0JUFuZHJleSBWLiBFbHN1a292IDxidTdjaGVyQHlhbmRleC5ydT6JATgEEwECACIFAkwB F1kCGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEAHF6gQQyKF6qmYIAI6ekfm1VA4T vqankI1ISE6ku4jV7UlpIQlEbE7/8n3Zd6teJ+pGOQhN5qk8QE7utdPdbktAzi+x7LIJVzUw 4TywZLXGrkP7VKYkfg6oyCGyzITghefQeJtr2TN4hYCkzPWpylkue8MtmqfZv/6royqwTbN+ +E09FQNvTgRUYJYTeQ1qOsxNRycwvw3dr2rOfuxShbzaHBB1pBIjGrMg8fC5pd65ACH5zuFV A0CoTNGMDrEZSfBkTW604UUHFFXeCoC3dwDZRKOWJ3GmMXns65Ai5YkA63BSHEE1Qle3VBhd cG1w0CB5FBV3pB27UVnf0jEbysrDqW4qN7XMRFSWNAy5AQ0ETAEXWQEIAJ2p6l9LBoqdH/0J PEFDY2t2gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+ LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cvoYxj3dz4 S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQravXpZkl5JG4eOqJVIU X316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhYkPKVn7z1sZiB7W2H2TojbmcK HZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUAEQEAAYkBHwQYAQIACQUCTAEXWQIbDAAK CRABxeoEEMihegkYCAC3ivGYNe2taNm/4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw 98OmX7G0OV9snxMW+6cyNqBrVFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQ WfyJJIM7l3gv5ZS3DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLoz BcFCNdDAyXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85JJrV1mi5i Message-ID: <1527ee44-334f-641f-cd78-ad2c54f9262d@yandex.ru> Date: Tue, 29 Jan 2019 00:07:56 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9ZWFQHJjkEuXZHZNvNymjGlzNUfzDLi5a" X-Rspamd-Queue-Id: 0E98E80130 X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yandex.ru header.s=mail header.b=SanRwLMa; dmarc=pass (policy=none) header.from=yandex.ru; spf=pass (mx1.freebsd.org: domain of bu7cher@yandex.ru designates 2a02:6b8:0:1472:2741:0:8b7:108 as permitted sender) smtp.mailfrom=bu7cher@yandex.ru X-Spamd-Result: default: False [-7.92 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[yandex.ru]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0:1000::/52]; HAS_ATTACHMENT(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yandex.ru:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yandex.ru,none]; MX_GOOD(-0.01)[cached: mx.yandex.ru]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.982,0]; RCVD_IN_DNSWL_LOW(-0.10)[8.0.1.0.7.b.8.0.0.0.0.0.1.4.7.2.2.7.4.1.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; FREEMAIL_ENVFROM(0.00)[yandex.ru]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yandex.ru.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[yandex.ru:s=mail]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; IP_SCORE(-1.73)[ipnet: 2a02:6b8::/32(-4.82), asn: 13238(-3.85), country: RU(0.00)]; TO_MATCH_ENVRCPT_SOME(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 21:11:20 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9ZWFQHJjkEuXZHZNvNymjGlzNUfzDLi5a Content-Type: multipart/mixed; boundary="egxmTT6MKsShC0i0JUDpySJ8sFPUxyY39"; protected-headers="v1" From: "Andrey V. Elsukov" To: Mark Saad Cc: FreeBSD Hackers Message-ID: <1527ee44-334f-641f-cd78-ad2c54f9262d@yandex.ru> Subject: Re: CPU Isolation References: <0e842838-e7d0-1b86-e27e-8d1562e70aee@yandex.ru> In-Reply-To: --egxmTT6MKsShC0i0JUDpySJ8sFPUxyY39 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 29.01.2019 00:01, Andrey V. Elsukov wrote: > As r331723 says, now kernel threads belong to cpuset #2, all other > processes belong to cpuset 1. So, you can try to use commands: > Limit all userlevel application to use only CPU cores 0-4: > # cpuset -s 1 -l 0-4 > Limit kernel level threads to use CPU only CPU cores 0-4: > # cpuset -s 2 -l 0-4 > and then dedicate CPUs 5-7 for your application with pid PID > # cpuset -l 5-7 -p PID Sorry, you need to create new set for your application, then you will be able to move it to CPU cores 5-7: # cpuset -C -l 5-7 -p PID --=20 WBR, Andrey V. Elsukov --egxmTT6MKsShC0i0JUDpySJ8sFPUxyY39-- --9ZWFQHJjkEuXZHZNvNymjGlzNUfzDLi5a Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlxPbywACgkQAcXqBBDI oXqjCQf/ZXndvQ54/HNGnGfou/fWlLiMhHG9utm529MvJCeKURSctzci30gqISpc yYyJSIuzfvA8LsUYF9NZ5nNuZ/SDZzLAUE8w75K9INJyVsEMg0RdSKMtYCCR7dva jV6IVfkWDqQ4NWSBX2UbCehLCMs8NK2O0JOeH1+UXW5ElZV2acW40gzZHEbS4w5k Zno0YqxD0HZ3Nj9sgnjAHxJriKDqx8tbAf8H4ABQdImUuX/W+axOPX7mX7E7jiRv ITcRbXEc8dz6nxBwAAyZs2w3nfQTcMcC8UIulEzcnYlrqgCA7M5taN9Q0RAnIK/m ZmkJyocT2LjNb7aA6lySz1oMBDi8zQ== =PVF/ -----END PGP SIGNATURE----- --9ZWFQHJjkEuXZHZNvNymjGlzNUfzDLi5a-- From owner-freebsd-hackers@freebsd.org Tue Jan 29 11:22:20 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08D8D14B8547 for ; Tue, 29 Jan 2019 11:22:20 +0000 (UTC) (envelope-from paul@prt.org) Received: from smtp3.mail.clearhost.co.uk (relay3.mail.clearhost.co.uk [IPv6:2001:1420::25:3]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.mail.clearhost.co.uk", Issuer "RapidSSL SHA256 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 66AD781675 for ; Tue, 29 Jan 2019 11:22:19 +0000 (UTC) (envelope-from paul@prt.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=prt.org; s=dkim1; 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=CW+lNyd9K5zZZor2yMhcx8eXa8FWKWQtDx3BLHBzXGQ=; b=ZW/93hLnGnPEu9wHHpU+P1uJaL +FTD99z7c4u3ud5ckEZG9qkA0J8+s+mZpdyWnJqOy2whM9tEtV6sN231myIj+zwj/R3NnArhECwgh N/1FCe3BRTo0WDFv6I6V2NSBONbSmmPTLkFdKj9v+aInu4pKop4L6r2K4zGP+5SEJ5bs=; Received: from [2001:1420:a:104:45:af22:4623:688e] (port=51923 helo=emma.prt.org) by smtp3.mail.clearhost.co.uk with esmtpsa (TLSv1:ECDHE-RSA-AES128-SHA:128) (Exim 4.90) (envelope-from ) id 1goRFX-000NF1-UB for freebsd-hackers@freebsd.org; Tue, 29 Jan 2019 11:08:16 +0000 To: freebsd-hackers@freebsd.org From: Paul Thornton Subject: Correct list for HAST issues Message-ID: <402f8c0f-9634-6b10-6e54-d02fe45c918c@prt.org> Date: Tue, 29 Jan 2019 11:22:16 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2019 11:22:20 -0000 Hi Hackers What is the concensus for the "correct" list to raise some HAST problems?  -net / -scsi / -geom or here? The high level view is that in 11.x, hastd exits because a "this can never happen" thing happens in primary.c - related to size of data returned by GGATE.  Under 12.0, this gets worse, but can still be worked around.  My main concern is that my "fix" just involves increasing buffer sizes without understanding what causes it to break in the first place, and that performance appears to suffer as a result. Bug 234576 relates to this problem. Paul. From owner-freebsd-hackers@freebsd.org Wed Jan 30 10:14:48 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60C0314BB0A3 for ; Wed, 30 Jan 2019 10:14:48 +0000 (UTC) (envelope-from emacsray@gmail.com) Received: from mail-ot1-f67.google.com (mail-ot1-f67.google.com [209.85.210.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64A048B1D5 for ; Wed, 30 Jan 2019 10:14:47 +0000 (UTC) (envelope-from emacsray@gmail.com) Received: by mail-ot1-f67.google.com with SMTP id n8so20633175otl.6 for ; Wed, 30 Jan 2019 02:14:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=p7M9MHHXCFc0u2EcWI/kuqTLZLUG8KNawNzuxhXXyEs=; b=YACeHOrv2ccRVRFkdJVtGllT6FYRDesxtXlhRDtY+sBpn9UW5mS40g6/+9DGyvrCil CKjuAdH2C5aM+SETU9W7nfcBY6ct4CcDKy2ILNnVawWSWgnUz6ZbSiTKXiQLswg91dO5 Szspn29LciPhttEAeoN7uqZHV2bVUwMHn/y9YGWxJf1UsxjJ8rVA7KQ5J44uMpQgNLgE 3B0KJuBW81n4+R8ifHHsC8tHtW6YBHSbfyYG+e3zqmd+L6BTQdVGK/rRqXJrVAIbTkjr 8wlmDyrLreb+GSgzHyVh4XwyZcjyIsOj/i78yliDYlfKaiasOzfJEeSPGsXT7FxSYu/Z tpWQ== X-Gm-Message-State: AJcUukeB6920jy1Vx9qEGQrj5iFM+j7zXffZ616ropr0sENQOQMv40EK onLvQB5K9FgAHDPkn9cGTohYl4MITN6Yf6Ioens= X-Google-Smtp-Source: ALg8bN6rCkvxFkUmJoPPbI/mQ71A7zxxO165nv/I6CQsLe562x+UHxUpEYBSeEKJbCq2FLnjH2MI9W7vaI/2rZsJ2No= X-Received: by 2002:a9d:7cd9:: with SMTP id r25mr21228114otn.110.1548842834342; Wed, 30 Jan 2019 02:07:14 -0800 (PST) MIME-Version: 1.0 From: Ray Date: Wed, 30 Jan 2019 18:07:03 +0800 Message-ID: Subject: Review llvm D55878 default to -Wl,--hash-style=gnu To: freebsd-toolchain@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 64A048B1D5 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of emacsray@gmail.com designates 209.85.210.67 as permitted sender) smtp.mailfrom=emacsray@gmail.com X-Spamd-Result: default: False [-3.80 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[67.210.85.209.rep.mailspike.net : 127.0.0.18]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.64)[-0.645,0]; RCVD_IN_DNSWL_NONE(0.00)[67.210.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.15)[ipnet: 209.85.128.0/17(-3.73), asn: 15169(-1.96), country: US(-0.07)]; FORGED_SENDER(0.30)[i@maskray.me,emacsray@gmail.com]; DMARC_NA(0.00)[maskray.me]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[i@maskray.me,emacsray@gmail.com]; FORGED_RECIPIENTS(0.00)[freebsd-toolchain@freebsd.org, freebsd-hackers@freebsd.org] X-Mailman-Approved-At: Wed, 30 Jan 2019 11:38:31 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2019 10:14:48 -0000 Can someone review this upstream clang change https://reviews.llvm.org/D55878 for default -Wl,--hash-style option used on FreeBSD? The current reviewers might be busy at the moment.. MIPS ABI require .dynsym to be s orted in a different way, but other architectures can benefit from this change (a few hundreds bytes to a few kilobytes for typical executables). From owner-freebsd-hackers@freebsd.org Wed Jan 30 23:13:18 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A308413326BD for ; Wed, 30 Jan 2019 23:13:18 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E9F5489813 for ; Wed, 30 Jan 2019 23:13:16 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id x0UNDDrb033016 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 30 Jan 2019 15:13:13 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id x0UNDDwr033015 for freebsd-hackers@freebsd.org; Wed, 30 Jan 2019 15:13:13 -0800 (PST) (envelope-from sgk) Date: Wed, 30 Jan 2019 15:13:13 -0800 From: Steve Kargl To: freebsd-hackers@freebsd.org Subject: Is libc C99 compliant? Message-ID: <20190130231313.GA27873@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: E9F5489813 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.50 / 15.00]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCVD_IN_DNSWL_MED(-0.20)[21.76.95.128.list.dnswl.org : 127.0.11.2]; MX_GOOD(-0.01)[cached: troutmask.apl.washington.edu]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.17)[ip: (0.41), ipnet: 128.95.0.0/16(0.42), asn: 73(0.10), country: US(-0.07)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.75)[0.755,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; NEURAL_SPAM_MEDIUM(0.94)[0.936,0]; RCPT_COUNT_ONE(0.00)[1]; AUTH_NA(1.00)[]; MIME_TRACE(0.00)[0:+]; NEURAL_SPAM_LONG(0.95)[0.950,0]; DMARC_NA(0.00)[washington.edu]; R_SPF_NA(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2019 23:13:19 -0000 Originally sent to freebsd-standards@ and freebsd-toolchain@, but those list appear to be defunct. Is libc C99 compliant? -- steve ----- Forwarded message from Steve Kargl ----- Date: Wed, 30 Jan 2019 13:29:04 -0800 From: Steve Kargl To: freebsd-standards@freebsd.org, freebsd-toolchain@freebsd.org Subject: Is libc C99 compliant? User-Agent: Mutt/1.11.2 (2019-01-07) When building gcc file gcc/config/freebsd.c contains #define TARGET_LIBC_HAS_FUNCTION no_c99_libc_has_function In targhook.c, one finds /* By default we assume that c99 functions are present at the runtime, but sincos is not. */ bool default_libc_has_function (enum function_class fn_class) { if (fn_class == function_c94 || fn_class == function_c99_misc || fn_class == function_c99_math_complex) return true; return false; } bool no_c99_libc_has_function (enum function_class fn_class ATTRIBUTE_UNUSED) { return false; } Shouldi/can TARGET_LIBC_HAS_FUNCTION be updated to at least default_libc_has_function? More importantly now that libm contains sincos[fl], should FreeBSD gcc config file be updated to use bool bsd_libc_has_function (enum function_class fn_class) { if (fn_class == function_c94 || fn_class == function_c99_misc || fn_class == function_c99_math_complex || fn_class == function_sincos) return true; return false; } -- Steve ----- End forwarded message ----- -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow