From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 11 13:32:45 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CF23A106566B for ; Sun, 11 Mar 2012 13:32:45 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 860488FC15 for ; Sun, 11 Mar 2012 13:32:45 +0000 (UTC) Received: by vcmm1 with SMTP id m1so3923060vcm.13 for ; Sun, 11 Mar 2012 06:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=OSgI7JRDqXmJOcgLOwc4An9MeZN7GMGyGgUfvrE0pqA=; b=thdqEp7ibv5cdFEuetW3eEtfTvGhW3ljGdXHwzO6/qJxjYIec6E0UMkiU2Idty8vpv i9XAAztXpiy9BBPaoZa/qwQdTaj/nmQtNFfC5HtHa3TztQIFCUiJrvgYIV3X1uKMmFGO HhqRD2aqSUlgyb682IsLIgrWKVdBmpCQWewjw0gO52mjKeHiHlljMNKeQK29cK5TBxhQ vNpwG12wSzHaTvWxgphcwbBRvecPsznJt81TH6E6AeKEHg69uybibGlUsXDlfbshIyFV DxSJvAtuvF+cqGL4rJd9Fdj+cL2WmyiKO3OpBc98x0omTr/5HPZRDxrYu/ogcTMyQ4dD VCWA== MIME-Version: 1.0 Received: by 10.52.23.169 with SMTP id n9mr12161434vdf.15.1331472764632; Sun, 11 Mar 2012 06:32:44 -0700 (PDT) Received: by 10.52.65.114 with HTTP; Sun, 11 Mar 2012 06:32:44 -0700 (PDT) In-Reply-To: <1930648073-1331401290-cardhu_decombobulator_blackberry.rim.net-1618036195-@b11.c1.bise3.blackberry> References: <1930648073-1331401290-cardhu_decombobulator_blackberry.rim.net-1618036195-@b11.c1.bise3.blackberry> Date: Sun, 11 Mar 2012 09:32:44 -0400 Message-ID: From: Robert Simmons To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: DKIM-Milter in Freebsd 9.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Mar 2012 13:32:45 -0000 On Sat, Mar 10, 2012 at 12:41 PM, Elman wrote: > Dear hacker, > > I install freebsd 9.0 release for the mail server, but no dkim-milter in = freebsd 9.0. I've been looking there, but it doesn't exist and only open-dk= im in freebsd 9.0. Is freebsd 9.0 no longer providing dkim-milter again in = freebsd port.? Before I was use freebsd 8.2 for mail server, there are stil= l exist dkim-milter. I finally install dkim-milter from source and manual c= ompile. According to the dkim-milter project website: "As of 2011-12-13, this project is no longer under active development." And: "NOTE: dkim-milter has been replaced by OpenDKIM, available at http://opendkim.org/" And from the OpenDKIM website: "The project started from a code fork of version 2.8.3 of the open source dkim-milter package developed and maintained by Sendmail, Inc." From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 11 15:45:51 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C4E3106564A for ; Sun, 11 Mar 2012 15:45:51 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CBAF58FC12 for ; Sun, 11 Mar 2012 15:45:50 +0000 (UTC) Received: by wern13 with SMTP id n13so821827wer.13 for ; Sun, 11 Mar 2012 08:45:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=hhwTaKf9GjFqKJqRTAdIZdpBVFWdflP3s0ScH/k49K0=; b=GaFWgLrYVVEKvmCCPasdBNe/N1mg9XalsG67QN5XnbqJ0xsBWnL5YGMiFWWbRAFG3m kNksJKuwfACtweOQIVXcS8T+gPkC+IWQ0UfGD3zb8uD0xJi5GccksurRfZh6Z1yEhnfE ecAKa8GlJ88OW8c7o+6pxkBlQ5G9bbKsf0PSnUWjXL2+nTFQexfHwKbO5XZm87LxEWJ+ kmKyCC5cDdrnxUZz7ssLYQ9krCe0pNSLmvB64VQe0oBiSr1cGy/i1wmqzckVbH1sXtc2 5C8NtMQbJA0odUBbzuY6kMsq+PpbzXLCGsQY434wVbz+P5mIKk6BmzT1brdae/6jQyas +XRg== MIME-Version: 1.0 Received: by 10.180.105.194 with SMTP id go2mr20166419wib.22.1331480749856; Sun, 11 Mar 2012 08:45:49 -0700 (PDT) Received: by 10.223.103.8 with HTTP; Sun, 11 Mar 2012 08:45:49 -0700 (PDT) Date: Sun, 11 Mar 2012 17:45:49 +0200 Message-ID: From: Vitaly Magerya To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: pmc(3): when are the counters updated? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Mar 2012 15:45:51 -0000 Hi, folks. I'm trying to use pmc(3) to analyze code fragments, and I've run into strange behavior: the counter values returned by pmc_read(3) sometimes show no increment between readings, but are updated a second later; even if the PMC in question was stopped before. Here's a test program: #include #include #include #include int main() { pmc_id_t pmcid; pmc_value_t value; int i; pmc_init(); pmc_allocate("instructions", PMC_MODE_TC, 0, PMC_CPU_ANY, &pmcid); pmc_start(pmcid); for (i = 0; i < 5000000; i++); pmc_stop(pmcid); pmc_read(pmcid, &value); printf("first reading: %lu\n", (unsigned long)value); sleep(1); pmc_read(pmcid, &value); printf("second reading: %lu\n", (unsigned long)value); } It's output on my system (FreeBSD 8.2 amd64, an Intel Atom processor) is something like this: first reading: 0 second reading: 15090110 I don't really like both numbers; I expect the first reading not to be zero (there obviously are instructions between pmc_start and pmc_stop), and I expect the second reading not to differ from the first, as the PMC was stopped before both of them, so it's value should not change. So, what's going on here? Is this the intended behavior, or can it be changed? And how do I get accurate readings? (BTW, is this the right list for such questions?) From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 00:58:10 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9AFE2106566B for ; Mon, 12 Mar 2012 00:58:10 +0000 (UTC) (envelope-from freebsd-hackers@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id DE4818FC0C for ; Mon, 12 Mar 2012 00:58:09 +0000 (UTC) Received: from mail.unitedinsong.com.au (bell.herveybayaustralia.com.au [192.168.0.40]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 235655C28 for ; Mon, 12 Mar 2012 11:11:40 +1000 (EST) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id E8FCA5C22 for ; Mon, 12 Mar 2012 11:11:39 +1000 (EST) Message-ID: <4F5D48E6.9010802@herveybayaustralia.com.au> Date: Mon, 12 Mar 2012 10:52:54 +1000 From: Da Rock <9Phackers@herveybayaustralia.com.au> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: "hackers@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 12 Mar 2012 02:33:11 +0000 Cc: Subject: Kernel memory usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "hackers@freebsd.org" List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 00:58:10 -0000 I may be required to move this to embedded, but I am only looking for generalisation. Recently a thread came up on questions regarding memory usage, and a post was made regarding wired memory being nearly all kernel- something I was ready to dispute, but then I thought I'd better make sure. So I tested a few theories first off: 1. Comparing memory usage across machines I checked servers and desktops as well as vm's for memory usage, and I found some interesting results. On a firewall with no apps installed only 35M wired is used, on a desktop up to 700M~ can be used. Even as a dedicated server with a few services used it remains around 35M. Surely this means that the wired memory used is not just kernel? But I held off my assumptions as it was still plausible that the structures used by the kernel could balloon that far, too. 2. Stripped down, lean mean, kernel machine I then (using a vm I was building a kernel for anyway) stripped down a kernel in a VBox VM using le drivers for network to see what could be achieved. This is my kernel conf: include GENERIC ident VPN options IPSEC options IPSEC_DEBUG options IPSEC_NAT_T device crypto device enc # minimise kernel nooptions UFS_GJOURNAL nooptions MD_ROOT nooptions NFSCL nooptions NFSD nooptions NFSLOCKD nooptions NFS_ROOT nooptions MSDOSFS nooptions CD9660 nooptions PROCFS nooptions PSEUDOFS nodevice fdc nodevice mvs nodevice siis nodevice ahc nodevice ahd nodevice esp nodevice hptiop nodevice isp nodevice mpt nodevice mps nodevice sym nodevice trm nodevice adv nodevice adw nodevice aic nodevice bt nodevice ses nodevice amr nodevice arcmsr nodevice ciss nodevice dpt nodevice hptmv nodevice hptrr nodevice irr nodevice ips nodevice mly nodevice twa nodevice aac nodevice aacp nodevice ida nodevice mfi nodevice mlx nodevice twe nodevice tws nodevice splash nodevice cbb nodevice pccard nodevice cardbus nodevice uart nodevice ppc nodevice ppbus nodevice lpt nodevice plip nodevice ppi nodevice puc nodevice bxe nodevice de nodevice em nodevice igb nodevice ixgbe nodevice ti nodevice txp nodevice vx nodevice miibus nodevice ae nodevice age nodevice alc nodevice ale nodevice bce nodevice bfe nodevice bge nodevice dc nodevice et nodevice fxp nodevice jme nodevice lge nodevice msk nodevice nfe nodevice nge nodevice pcn nodevice re nodevice rl nodevice sf nodevice sge nodevice sis nodevice sk nodevice ste nodevice stge nodevice tl nodevice tx nodevice vge nodevice vr nodevice wb nodevice xl nodevice cs nodevice ed nodevice ex nodevice ep nodevice fe nodevice sn nodevice xe nodevice wlan nooptions IEEE80211_DEBUG nooptions IEEE80211_AMPDU_AGE nooptions IEEE80211_SUPPORT_MESH nodevice wlan_wep nodevice wlan_ccmp nodevice wlan_tkip nodevice wlan_amrr nodevice an nodevice ath nodevice ath_pci nodevice ath_hal nooptions AH_SUPPORT_AR5416 nodevice ath_rate_sample nodevice ipw nodevice iwi nodevice iwn nodevice malo nodevice mwl nodevice ral nodevice wi nodevice wpi nodevice md nooption USB_DEBUG nodevice uhci nodevice ohci nodevice ehci nodevice xhci nodevice usb nodevice uhid nodevice ukbd nodevice ulpt nodevice umass nodevice ums nodevice urio nodevice u3g nodevice uark nodevice ubsa nodevice uftdi nodevice uipaq nodevice uplcom nodevice uslcom nodevice uvisor nodevice uvscom nodevice aue nodevice axe nodevice cdce nodevice cue nodevice kue nodevice rue nodevice udav nodevice rum nodevice run nodevice uath nodevice upgt nodevice ural nodevice urtw nodevice zyd #nodevice firewire nodevice fwe nodevice fwip #nodevice dcons #nodevice dcons_rom nodevice sound nodevice snd_es137x nodevice snd_hda nodevice snd_ich nodevice snd_uaudio nodevice snd_via8233 World was also rebuilt as recommended by the handbook. As you can see I was rebuilding for IPSEC (for testing purposes only note). I couldn't remove dcons (not sure why- missing defined references), and that pulled in firewire too. The result was surprising: a 14M kernel became 6.3M, and when running I found it only used 19M used for wired (whoopee!) as opposed to 35M. No services were running per se, only the usual suspects in base: vpn-test# ps ax PID TT STAT TIME COMMAND 0 ?? DLs 0:00.11 [kernel] 1 ?? ILs 0:00.01 /sbin/init -- 2 ?? DL 0:00.00 [crypto] 3 ?? DL 0:00.00 [crypto returns] 4 ?? DL 0:00.00 [sctp_iterator] 5 ?? DL 0:00.00 [xpt_thrd] 6 ?? DL 0:00.10 [pagedaemon] 7 ?? DL 0:00.00 [vmdaemon] 8 ?? DL 0:00.01 [pagezero] 9 ?? DL 0:00.30 [bufdaemon] 10 ?? DL 0:00.00 [audit] 11 ?? RL 589:34.00 [idle] 12 ?? WL 0:38.64 [intr] 13 ?? DL 0:12.21 [geom] 14 ?? DL 0:03.30 [yarrow] 15 ?? DL 0:04.40 [syncer] 16 ?? DL 0:00.63 [vnlru] 17 ?? DL 0:00.53 [softdepflush] 104 ?? Is 0:00.00 adjkerntz -i 582 ?? Is 0:00.00 /sbin/devd 737 ?? Ss 0:00.09 /usr/sbin/syslogd -s 912 ?? Ss 0:02.68 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid 977 ?? Is 0:00.00 /usr/sbin/sshd 984 ?? Ss 0:00.81 sendmail: accepting connections (sendmail) 988 ?? Is 0:00.01 sendmail: Queue runner@00:30:00 for /var/spool/client 994 ?? Ss 0:00.12 /usr/sbin/cron -s 2061 ?? Is 0:00.03 sshd: admin [priv] (sshd) 2064 ?? S 0:00.04 sshd: admin@pts/0 (sshd) 1052 v0 Is 0:00.01 login [pam] (login) 1060 v0 I+ 0:00.02 -csh (csh) 1053 v1 Is+ 0:00.00 /usr/libexec/getty Pc ttyv1 1054 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2 1055 v3 Is+ 0:00.00 /usr/libexec/getty Pc ttyv3 1056 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4 1057 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5 1058 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6 1059 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7 2065 0 Is 0:00.02 -csh (csh) 2068 0 I 0:00.01 su 2069 0 S 0:00.04 _su (csh) 2414 0 R+ 0:00.00 ps ax After some minutes though, the usage went up to 39M. WTF? So I'm now thoroughly confused. Google didn't really show up any real answers either. Aside from discovering the true nature of what was discussed in the posts, my hypothetical theorising is for my own academics as well; and I'm trying to slim down my kernels to see if I can improve performance with low memory systems. Can process structures cause this much ballooning? I find that hard to believe given not much is running here. My only other thought would be pipe or network structures? Anything I'm missing? FWIW, my trimmed down, slim and slender, aerodynamic kernel can boot in seconds as opposed to minutes. Sweet! Although compiling clang took years... and gcc was built as well :/ Cheers From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 09:03:38 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A908C106566B for ; Mon, 12 Mar 2012 09:03:38 +0000 (UTC) (envelope-from fabien.thomas@netasq.com) Received: from work.netasq.com (mars.netasq.com [91.212.116.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2161C8FC0A for ; Mon, 12 Mar 2012 09:03:37 +0000 (UTC) Received: from [10.2.1.103] (unknown [10.2.1.103]) by work.netasq.com (Postfix) with ESMTPSA id D275774004C; Mon, 12 Mar 2012 10:02:06 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: multipart/signed; boundary="Apple-Mail=_D3015E11-0567-4272-83FF-B445D0D19193"; protocol="application/pkcs7-signature"; micalg=sha1 From: Fabien Thomas In-Reply-To: Date: Mon, 12 Mar 2012 10:03:35 +0100 Message-Id: References: To: Vitaly Magerya X-Mailer: Apple Mail (2.1257) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: pmc(3): when are the counters updated? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 09:03:38 -0000 --Apple-Mail=_D3015E11-0567-4272-83FF-B445D0D19193 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Le 11 mars 2012 =E0 16:45, Vitaly Magerya a =E9crit : > Hi, folks. I'm trying to use pmc(3) to analyze code fragments, and > I've run into strange behavior: the counter values returned by > pmc_read(3) sometimes show no increment between readings, but are > updated a second later; even if the PMC in question was stopped > before. >=20 > Here's a test program: >=20 > #include > #include > #include > #include >=20 > int main() { > pmc_id_t pmcid; > pmc_value_t value; > int i; >=20 > pmc_init(); > pmc_allocate("instructions", PMC_MODE_TC, 0, PMC_CPU_ANY, = &pmcid); > pmc_start(pmcid); > for (i =3D 0; i < 5000000; i++); > pmc_stop(pmcid); > pmc_read(pmcid, &value); > printf("first reading: %lu\n", (unsigned long)value); > sleep(1); > pmc_read(pmcid, &value); > printf("second reading: %lu\n", (unsigned long)value); > } >=20 > It's output on my system (FreeBSD 8.2 amd64, an Intel Atom processor) > is something like this: >=20 > first reading: 0 > second reading: 15090110 >=20 > I don't really like both numbers; I expect the first reading not > to be zero (there obviously are instructions between pmc_start and > pmc_stop), and I expect the second reading not to differ from the > first, as the PMC was stopped before both of them, so it's value > should not change. >=20 > So, what's going on here? Is this the intended behavior, or can it > be changed? And how do I get accurate readings? If i remember well: The current code will get real HW PMC if the PMC is running and attached = to owner. The first case is not true in your code so you get the saved value which = is updated at process switch out time. I think you can do: pmc_read pmc_stop. >=20 > (BTW, is this the right list for such questions?) > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" --Apple-Mail=_D3015E11-0567-4272-83FF-B445D0D19193-- From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 06:42:08 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99F92106566B for ; Mon, 12 Mar 2012 06:42:08 +0000 (UTC) (envelope-from czsq888@163.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 749A78FC14 for ; Mon, 12 Mar 2012 06:42:08 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1S6yiF-0003PA-Mi for freebsd-hackers@freebsd.org; Sun, 11 Mar 2012 23:26:31 -0700 Date: Sun, 11 Mar 2012 23:26:31 -0700 (PDT) From: sw2wolf To: freebsd-hackers@freebsd.org Message-ID: <1331533591697-5556741.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Mon, 12 Mar 2012 11:30:09 +0000 Subject: How to mount my USB disk ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 06:42:08 -0000 Once plugged, usbconfig will show: ugen0.1: at usbus0, cfg=3D0 md=3DHOST spd=3DFULL (12= Mbps)=20 pwr=3DSAVE=20 ugen1.1: at usbus1, cfg=3D0 md=3DHOST spd=3DHIGH (48= 0Mbps) pwr=3DSAVE ugen0.2: at usbus0, cfg=3D0 md=3DHOST spd=3DFULL= (12M) pwr=3DSAVE ugen1.2: at usbus1, cfg=3D0 md=3DHOST spd= =3DHIGH (480Mbps) pwr=3DON But there is no da* in /dev, then i donot know how to mount it ? Sincerely! ----- e^(=CF=80.i) + 1 =3D 0 -- View this message in context: http://freebsd.1045724.n5.nabble.com/How-to-m= ount-my-USB-disk-tp5556741p5556741.html Sent from the freebsd-hackers mailing list archive at Nabble.com. From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 12:40:03 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 524A61065670 for ; Mon, 12 Mar 2012 12:40:03 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id B87318FC08 for ; Mon, 12 Mar 2012 12:40:02 +0000 (UTC) Received: by lboi15 with SMTP id i15so1312855lbo.13 for ; Mon, 12 Mar 2012 05:40:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=HGEU955jAAA5xI1sRgB1H3S3mSIRI4RdOLTWjR2ESnk=; b=q6hMx6KFl8Lxhf1K7CJq1vDk+1k4UajX5LcE3rsssaSMtaZt+AFAxR4lnLxYRF9hvw Kd7lH7CIjTfg4anKXF1sQG7KHgZRRF8hYsf4OppmEyPfVlGg2Jgn6Ad28bTfyzyYyX4c AXhdZFOWCgJgdi9+ChRVKzi0fiUabj4h/0Ax1Bob5d8JJzMw4VqBt0NwGNnCy4M6LLEp E3mBnFtWvi+2xx8Co6wsucA1tnKGVGkIMjiY+CFfYY+vGfT5CjEld/CzIVww3xM0GZhx hS1RoHmChV2UBzae/ojQuVWgQiKTJFYkagnlNrsjpw796nfc08GFTgwHcwTgu6fjlz5E W1Tg== Received: by 10.152.103.239 with SMTP id fz15mr9079481lab.42.1331556001409; Mon, 12 Mar 2012 05:40:01 -0700 (PDT) Received: from [172.29.1.142] (altimet-gw.cs2.dp.wnet.ua. [217.20.178.249]) by mx.google.com with ESMTPS id v4sm18208569lbx.13.2012.03.12.05.39.59 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Mar 2012 05:40:00 -0700 (PDT) Message-ID: <4F5DEE7E.5030008@gmail.com> Date: Mon, 12 Mar 2012 14:39:26 +0200 From: Vitaly Magerya User-Agent: Thunderbird MIME-Version: 1.0 To: Fabien Thomas References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: pmc(3): when are the counters updated? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 12:40:03 -0000 Fabien Thomas wrote: >> So, what's going on here? Is this the intended behavior, or can it >> be changed? And how do I get accurate readings? > > If i remember well: > The current code will get real HW PMC if the PMC is running and attached to owner. > The first case is not true in your code so you get the saved value which is updated at > process switch out time. > > I think you can do: > pmc_read > pmc_stop. Changing the code to this: [...] pmc_read(pmcid, &value); pmc_stop(pmcid); printf("reading #1: %lu\n", (unsigned long)value); pmc_read(pmcid, &value); printf("reading #2: %lu\n", (unsigned long)value); sleep(1); pmc_read(pmcid, &value); printf("reading #3: %lu\n", (unsigned long)value); [...] Gives me this output: reading #1: 15039441 reading #2: 0 reading #3: 15084037 So, it seems that you are correct; pmc_read reports current values if the PMC is not stopped, after which it's updated on context switches. From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 13:04:09 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9168106566B for ; Mon, 12 Mar 2012 13:04:09 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C55A8FC0A for ; Mon, 12 Mar 2012 13:04:09 +0000 (UTC) Received: by wern13 with SMTP id n13so1751705wer.13 for ; Mon, 12 Mar 2012 06:04:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Qa9HMWRLuVyuyWrAOiOTeFVtfjjsSqJyDZbvzvutAIE=; b=HKJPESZbl1cdn1dRcEFy6q/zgui9ap0MMqtD6cCGwa5ulBRV3TNcly3DeUq7WOeaZT lx/IqFJwwpBLYrDCVE8AsYIx8rN1fFaaKtuNIIFqOg4i28wjdq+Tt+OJvM6UPgSryR7b MVOXBROvfpzBPwUnj5dNVgml6SI0A9oyRhJHMNXMUAQtlbBrSYr7kPK62J0XlUcrP5rF sMKebtIiL4aRJ4xcWdDwv16ItZuLpgfHR/KF+/zIFku6DcB2j7B0ziMezfx5lozoE6Ow Zj/cJCl7KnOwxAHtwKscI+DUsuhPRjI59xRDaX6liF44yRZA2BndbTNrqrd5bpyoIDgZ 0oOg== MIME-Version: 1.0 Received: by 10.216.131.2 with SMTP id l2mr7162996wei.3.1331557448303; Mon, 12 Mar 2012 06:04:08 -0700 (PDT) Received: by 10.216.48.5 with HTTP; Mon, 12 Mar 2012 06:04:08 -0700 (PDT) In-Reply-To: <4F5DEE7E.5030008@gmail.com> References: <4F5DEE7E.5030008@gmail.com> Date: Mon, 12 Mar 2012 14:04:08 +0100 Message-ID: From: Harald Servat To: Vitaly Magerya Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, Fabien Thomas Subject: Re: pmc(3): when are the counters updated? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 13:04:09 -0000 2012/3/12 Vitaly Magerya > Fabien Thomas wrote: > >> So, what's going on here? Is this the intended behavior, or can it > >> be changed? And how do I get accurate readings? > > > > If i remember well: > > The current code will get real HW PMC if the PMC is running and attached > to owner. > > The first case is not true in your code so you get the saved value which > is updated at > > process switch out time. > > > > I think you can do: > > pmc_read > > pmc_stop. > > Changing the code to this: > > [...] > pmc_read(pmcid, &value); > pmc_stop(pmcid); > printf("reading #1: %lu\n", (unsigned long)value); > pmc_read(pmcid, &value); > printf("reading #2: %lu\n", (unsigned long)value); > sleep(1); > pmc_read(pmcid, &value); > printf("reading #3: %lu\n", (unsigned long)value); > [...] > > Gives me this output: > > reading #1: 15039441 > reading #2: 0 > reading #3: 15084037 > > So, it seems that you are correct; pmc_read reports current values if > the PMC is not stopped, after which it's updated on context switches. > > Hello, I've used the PMC library in the past, and I think that you can't stop the counters if you want to read them. By having them started, you can read their value anywhere in the code, not only in context switches. I suggest you changing the code to something like pmc_read(..); do_some_calculation(..); pmc_read(..); /* difference between reads is devoted to do_some_calculation */ and when you're about to finalize the application, issue pmc_stop. Please, also note, sleep(1) yields the process, so counting it (even if it's 1 second or more) will probably result in very low counter values. Regards -- Fry: You can see how I lived before I met you. Bender: You lived before you met me?! Fry: Yeah, lots of people did. Bender: Really?! From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 15:01:05 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09BF6106564A for ; Mon, 12 Mar 2012 15:01:05 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id C0A6F8FC0C for ; Mon, 12 Mar 2012 15:01:04 +0000 (UTC) Received: by yhgm50 with SMTP id m50so3142118yhg.13 for ; Mon, 12 Mar 2012 08:00:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UrFWM2eOdKm98zU/IIKOiFjhVL7Zx/4r/oobUPCqkAM=; b=MEDpnG2LHZBeUA4yutng/Z/wBIZzJfOf0prQYNQChb9Vx4QkaVj7jEXoa6UzxKKpA4 inUvxTZyJiDafRmQhoAys9B2aDE8e+4suAiEHBpMxvkxQG3BYTwaK9NbWrYlaqmOOxc7 CDpYK50YbpsAWbEJXQh2a2NXMFGERKaw+t/yxHMVCXTrdK3pPO8AY1wBy0ewp9wvkrtc T4oUFt0eAFk8VMBD0UeVmr+e7bO0ixkvRNKuepT6ovYfG8+XVtfLHrdMToh/Xo+iwJxd OxzsyziT/pchGD4s64jPoRnfkwsAmCZeDg0fZnEDsl2f9mQtXllNTWhqGtdVy0nNoYYG PeTw== MIME-Version: 1.0 Received: by 10.236.177.6 with SMTP id c6mr13586171yhm.42.1331564458798; Mon, 12 Mar 2012 08:00:58 -0700 (PDT) Received: by 10.236.75.162 with HTTP; Mon, 12 Mar 2012 08:00:58 -0700 (PDT) Date: Mon, 12 Mar 2012 16:00:58 +0100 Message-ID: From: Svatopluk Kraus To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: [vfs] buf_daemon() slows down write() severely on low-speed CPU X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 15:01:05 -0000 Hi, I have solved a following problem. If a big file (according to 'hidirtybuffers') is being written, the write speed is very poor. It's observed on system with elan 486 and 32MB RAM (i.e., low speed CPU and not too much memory) running FreeBSD-9. Analysis: A file is being written. All or almost all dirty buffers belong to the file. The file vnode is almost all time locked by writing process. The buf_daemon() can not flush any dirty buffer as a chance to acquire the file vnode lock is very low. A number of dirty buffers grows up very slow and with each new dirty buffer slower, because buf_daemon() eats more and more CPU time by looping on dirty buffers queue (with very low or no effect). This slowing down effect is started by buf_daemon() itself, when 'numdirtybuffers' reaches 'lodirtybuffers' threshold and buf_daemon() is waked up by own timeout. The timeout fires at 'hz' period, but starts to fire at 'hz/10' immediately as buf_daemon() fails to reach 'lodirtybuffers' threshold. When 'numdirtybuffers' (now slowly) reaches ((lodirtybuffers + hidirtybuffers) / 2) threshold, the buf_daemon() can be waked up within bdwrite() too and it's much worse. Finally and with very slow speed, the 'hidirtybuffers' or 'dirtybufthresh' is reached, the dirty buffers are flushed, and everything starts from beginning... On the system, a buffer size is 512 bytes and the default thresholds are following: vfs.hidirtybuffers = 134 vfs.lodirtybuffers = 67 vfs.dirtybufthresh = 120 For example, a 2MB file is copied into flash disk in about 3 minutes and 15 second. If dirtybufthresh is set to 40, the copy time is about 20 seconds. My solution is a mix of three things: 1. Suppresion of buf_daemon() wakeup by setting bd_request to 1 in the main buf_daemon() loop. 2. Increment of buf_daemon() fast timeout from hz/10 to hz/4. 3. Tuning dirtybufthresh to (((lodirtybuffers + hidirtybuffers) / 2) - 15) magic. The mention copy time is about 30 seconds now. The described problem is just for information to anyone who can be interested in. Comments are welcome. However, the bd_request thing is more general. bd_request (despite its description) should be 0 only when buf_daemon() is in sleep(). Otherwise, wakeup() on &bd_request channel is useless. Therefore, setting bd_request to 1 in the main buf_daemon() loop is correct and better as it saves time spent by wakeup() on not existing channel. Svata From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 15:57:52 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC0A61065728 for ; Mon, 12 Mar 2012 15:57:48 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 47C7E8FC0C for ; Mon, 12 Mar 2012 15:57:48 +0000 (UTC) Received: by ggnk4 with SMTP id k4so3244175ggn.13 for ; Mon, 12 Mar 2012 08:57:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lK182WWb1gup7o4ZXorXQHRkIVpZlyTaZzR71BhBbLE=; b=oZiQMH7cWJ6u7JJ/zc9TbqIaBHzYVLvuyyImGm5XORuGucmuXYFgZV+xIoqwrOpuhK NkREUaDR8/lrNYliqrBgvx82X6YgXgchq1q5r3WY60Dvr60uHHLYSmaAmxiXumWuuSz0 CwTrFRm3tMrffcnaqwl4oT3c+5N/mQkuymtPIAM8OL5ngWuNLSvgo7XVHU59CpyDfZcH 2apCkEEbNjtwkgoYn5RcPScUuOrbiaQkrbHe9erRCYpgzAak3GPV3L2F1NFVEK74WNXg 0V2Xg1wgmtiXVbVEj392HYSM0fQnposuBW+cfSUnpLgsoseDpbvxTZ6MsZnzSlF6xkVP Nw4Q== MIME-Version: 1.0 Received: by 10.101.175.14 with SMTP id c14mr4258558anp.39.1331567867845; Mon, 12 Mar 2012 08:57:47 -0700 (PDT) Received: by 10.236.75.162 with HTTP; Mon, 12 Mar 2012 08:57:47 -0700 (PDT) Date: Mon, 12 Mar 2012 16:57:47 +0100 Message-ID: From: Svatopluk Kraus To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: pccbb device doesn't send device_shutdown() to childs (reboot freezes) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 15:57:52 -0000 Hi, I solved very curious problem with rarely system (FreeBSD-9) freezing during reboot. Finally, I found out that system freezes in ep device callout. The part of device tree is following: -> pccbb -> pccard -> ep cbb_pci_shutdown() method in pccbb device places the cards in reset, turns off the interrupts and powers down the socket. No child has a chance to know about it. Thus, if ep device callout fires between device_shutdown() is called on root device and interrupts are disabled, the callout freezes in never-ending while loop, which reads status from hardware (now without power). I propose following change (editted by hand) in cbb_pci_shutdown(): struct cbb_softc *sc = (struct cbb_softc *)device_get_softc(brdev); + + /* Inform all childs. */ + bus_generic_shutdown(brdev); + /* * We're about to pull the rug out from the card, so mark it as * gone to prevent harm. */ sc->cardok = 0; Futhermore, ep device (ed device too, ... ?) has not implemented device_shutdown method. So, fixing pccbb device is not enough to solve the freezing problem. I somehow patched the mentioned devices too, but maybe someone more competent should do it for FreeBSD tree. Svata From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 18:19:30 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 511B7106566C for ; Mon, 12 Mar 2012 18:19:30 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id D78348FC0A for ; Mon, 12 Mar 2012 18:19:29 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q2CIJMX7030536; Mon, 12 Mar 2012 20:19:22 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q2CIJL0W031582; Mon, 12 Mar 2012 20:19:21 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q2CIJLkQ031581; Mon, 12 Mar 2012 20:19:21 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 12 Mar 2012 20:19:21 +0200 From: Konstantin Belousov To: Svatopluk Kraus Message-ID: <20120312181921.GF75778@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sFvwHbI2VNbToG61" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: hackers@freebsd.org Subject: Re: [vfs] buf_daemon() slows down write() severely on low-speed CPU X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 18:19:30 -0000 --sFvwHbI2VNbToG61 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 12, 2012 at 04:00:58PM +0100, Svatopluk Kraus wrote: > Hi, >=20 > I have solved a following problem. If a big file (according to > 'hidirtybuffers') is being written, the write speed is very poor. >=20 > It's observed on system with elan 486 and 32MB RAM (i.e., low speed > CPU and not too much memory) running FreeBSD-9. >=20 > Analysis: A file is being written. All or almost all dirty buffers > belong to the file. The file vnode is almost all time locked by > writing process. The buf_daemon() can not flush any dirty buffer as a > chance to acquire the file vnode lock is very low. A number of dirty > buffers grows up very slow and with each new dirty buffer slower, > because buf_daemon() eats more and more CPU time by looping on dirty > buffers queue (with very low or no effect). >=20 > This slowing down effect is started by buf_daemon() itself, when > 'numdirtybuffers' reaches 'lodirtybuffers' threshold and buf_daemon() > is waked up by own timeout. The timeout fires at 'hz' period, but > starts to fire at 'hz/10' immediately as buf_daemon() fails to reach > 'lodirtybuffers' threshold. When 'numdirtybuffers' (now slowly) > reaches ((lodirtybuffers + hidirtybuffers) / 2) threshold, the > buf_daemon() can be waked up within bdwrite() too and it's much worse. > Finally and with very slow speed, the 'hidirtybuffers' or > 'dirtybufthresh' is reached, the dirty buffers are flushed, and > everything starts from beginning... Note that for some time, bufdaemon work is distributed among bufdaemon thread itself and any thread that fails to allocate a buffer, esp. a thread that owns vnode lock and covers long queue of dirty buffers. >=20 > On the system, a buffer size is 512 bytes and the default > thresholds are following: >=20 > vfs.hidirtybuffers =3D 134 > vfs.lodirtybuffers =3D 67 > vfs.dirtybufthresh =3D 120 >=20 > For example, a 2MB file is copied into flash disk in about 3 > minutes and 15 second. If dirtybufthresh is set to 40, the copy time > is about 20 seconds. >=20 > My solution is a mix of three things: > 1. Suppresion of buf_daemon() wakeup by setting bd_request to 1 in > the main buf_daemon() loop. I cannot understand this. Please provide a patch that shows what do you mean there. > 2. Increment of buf_daemon() fast timeout from hz/10 to hz/4. > 3. Tuning dirtybufthresh to (((lodirtybuffers + hidirtybuffers) / > 2) - 15) magic. Even hz / 10 is awfully long time on modern hardware. The dirtybufthresh is already the sysctl that you can change. The 32MB is indeed around the lowest amount of memory where recent FreeBSD can make an illusion of being useful. I am not sure how much should the system be tuned by default for such configuration. >=20 > The mention copy time is about 30 seconds now. >=20 > The described problem is just for information to anyone who can be > interested in. Comments are welcome. However, the bd_request thing is > more general. >=20 > bd_request (despite its description) should be 0 only when > buf_daemon() is in sleep(). Otherwise, wakeup() on &bd_request channel > is useless. Therefore, setting bd_request to 1 in the main > buf_daemon() loop is correct and better as it saves time spent by > wakeup() on not existing channel. >=20 > Svata > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" --sFvwHbI2VNbToG61 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk9ePikACgkQC3+MBN1Mb4g94ACdHGCcO1o/TXTmOUMrra7wJpJF lh8Anj+gEcJVhbFMnNi3o8mIFbbV7790 =J4sI -----END PGP SIGNATURE----- --sFvwHbI2VNbToG61-- From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 18:23:38 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79C721065672 for ; Mon, 12 Mar 2012 18:23:38 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 039A48FC24 for ; Mon, 12 Mar 2012 18:23:37 +0000 (UTC) Received: by lagv3 with SMTP id v3so5285508lag.13 for ; Mon, 12 Mar 2012 11:23:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=XLGx/5HsEkIGHEok9snQfHMfEuIs2p/ZkzlptjkFl8c=; b=tCa09DfpZSQm/QbfYAYdYz/WUem8sRJYfQDpZI/0Fx5KbxfYdtu1YiM8mVSPWvO7KI x9M/TRIknBFtrSkocKJCcXD0QVxNLIMqmoR1OFBesFmkMskeC111c3Y9EX5jLDTE8Mde q4ce8CcQyt0zYyp30dsQZyuiq9j823WttvyUuhnywCJT7R+Z/JrNIoHmebzh+UhRpUkm u9XPFPBQaNi5kC2F0JGFNS2cdc9l4XDE11GqvnM5+SduKKdsipJP2r7GNO4LmZ8Ktl+z ZhIZ7TkrO9tQ26qM8vRJ7B/f+1vEBd6z0QlDudncTAbJ+ufPGkvhyt9Y22eQKpKRpHNu VCHg== MIME-Version: 1.0 Received: by 10.112.105.39 with SMTP id gj7mr5105841lbb.23.1331576616791; Mon, 12 Mar 2012 11:23:36 -0700 (PDT) Received: by 10.152.13.72 with HTTP; Mon, 12 Mar 2012 11:23:36 -0700 (PDT) Date: Mon, 12 Mar 2012 19:23:36 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: FreeBSD Hackers Content-Type: text/plain; charset=ISO-8859-1 Subject: hack.So: could not read symbols X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 18:23:38 -0000 I'm using 9.0-RELEASE. I downloaded the snapshot "9.0-CURRENT-201012" and tried to build it's kernel but I get this error: hack.So: could not read symbols: File in wrong format file reports this: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped I compared this file with the same file generated during the compilation of the 9.0-RELEASE GENERIC kernel and they are identical. What's the problem here? Thanks in advance From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 19:40:18 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B1431065673 for ; Mon, 12 Mar 2012 19:40:18 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id DECCC8FC16 for ; Mon, 12 Mar 2012 19:40:17 +0000 (UTC) Received: by yhgm50 with SMTP id m50so3511574yhg.13 for ; Mon, 12 Mar 2012 12:40:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A7uriAh/eIsXg507UGbi+Vv+/VUwRcu+YMpngaxOoNw=; b=YLazVVWzhLo2idxtzqYNAhOCZLvMxanladTludlH3ZP36eFDB0NzvhhwBhpMeya7VR TcfCXYSHh4Sbc+a2RKEklkd9yOD0hN8rqieQE4PvS6PI276KPC3h09LRcin589SC/RP7 i2Le0Y3/jFZo8OXmQuFkHFonjIs0sNQg2lmPg1cFs7uJLjCNTOw4DBm8+rfdYVxJbbun m2OaxPWrHfJ60QHjxW8tcw1cqZ6aK3+T5q0oH2i6ZsmZPC6PUTpSDVNvpXorVE824qOw WcYQOAVFLIciifhBnp/maIpFzPvCNdyQAI7jUcHfn8w2LiAXmZWX6D9WT2HVcMPGkrsq 7n2A== MIME-Version: 1.0 Received: by 10.68.189.5 with SMTP id ge5mr2577271pbc.50.1331581217134; Mon, 12 Mar 2012 12:40:17 -0700 (PDT) Received: by 10.68.208.168 with HTTP; Mon, 12 Mar 2012 12:40:17 -0700 (PDT) In-Reply-To: <4F5D48E6.9010802@herveybayaustralia.com.au> References: <4F5D48E6.9010802@herveybayaustralia.com.au> Date: Mon, 12 Mar 2012 15:40:17 -0400 Message-ID: From: Super Bisquit To: "hackers@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Cc: 9Phackers@herveybayaustralia.com.au Subject: Re: Kernel memory usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 19:40:18 -0000 CPU architecture and model have a lot to do with performance. You will also get different results if you used qemu in place of VirtualBox. Qemu allows you to choose different emulated architectures, CPUs, and machine bases. What's the downside? You have to use the command line. Install qemu and run a series of virtual machines. Embedded devices also include Power(PC), ARMv?, Coldfire, et al; you're only dealing with i386 and/or the 64 bit extension (AMD64). CISC- which does not contain any hardware modification to be a RISC replacement- runs fewer instructions than RISC due to the limited number of registers. Take this into consideration every time a program runs. Everything else also matters on real and emulated systems: Is it ide, scsi, sdd, flashdevice for the hard drive? What type of RAM? Dedicated or shared disk? On 3/11/12, Da Rock <9Phackers@herveybayaustralia.com.au> wrote: > I may be required to move this to embedded, but I am only looking for > generalisation. > > Recently a thread came up on questions regarding memory usage, and a > post was made regarding wired memory being nearly all kernel- something > I was ready to dispute, but then I thought I'd better make sure. > > So I tested a few theories first off: > > 1. Comparing memory usage across machines > > I checked servers and desktops as well as vm's for memory usage, and I > found some interesting results. On a firewall with no apps installed > only 35M wired is used, on a desktop up to 700M~ can be used. Even as a > dedicated server with a few services used it remains around 35M. > > Surely this means that the wired memory used is not just kernel? But I > held off my assumptions as it was still plausible that the structures > used by the kernel could balloon that far, too. > > 2. Stripped down, lean mean, kernel machine > > I then (using a vm I was building a kernel for anyway) stripped down a > kernel in a VBox VM using le drivers for network to see what could be > achieved. This is my kernel conf: > > include GENERIC > ident VPN > options IPSEC > options IPSEC_DEBUG > options IPSEC_NAT_T > device crypto > device enc > > # minimise kernel > nooptions UFS_GJOURNAL > nooptions MD_ROOT > nooptions NFSCL > nooptions NFSD > nooptions NFSLOCKD > nooptions NFS_ROOT > nooptions MSDOSFS > nooptions CD9660 > nooptions PROCFS > nooptions PSEUDOFS > nodevice fdc > nodevice mvs > nodevice siis > nodevice ahc > nodevice ahd > nodevice esp > nodevice hptiop > nodevice isp > nodevice mpt > nodevice mps > nodevice sym > nodevice trm > nodevice adv > nodevice adw > nodevice aic > nodevice bt > nodevice ses > nodevice amr > nodevice arcmsr > nodevice ciss > nodevice dpt > nodevice hptmv > nodevice hptrr > nodevice irr > nodevice ips > nodevice mly > nodevice twa > nodevice aac > nodevice aacp > nodevice ida > nodevice mfi > nodevice mlx > nodevice twe > nodevice tws > nodevice splash > nodevice cbb > nodevice pccard > nodevice cardbus > nodevice uart > nodevice ppc > nodevice ppbus > nodevice lpt > nodevice plip > nodevice ppi > nodevice puc > nodevice bxe > nodevice de > nodevice em > nodevice igb > nodevice ixgbe > nodevice ti > nodevice txp > nodevice vx > nodevice miibus > nodevice ae > nodevice age > nodevice alc > nodevice ale > nodevice bce > nodevice bfe > nodevice bge > nodevice dc > nodevice et > nodevice fxp > nodevice jme > nodevice lge > nodevice msk > nodevice nfe > nodevice nge > nodevice pcn > nodevice re > nodevice rl > nodevice sf > nodevice sge > nodevice sis > nodevice sk > nodevice ste > nodevice stge > nodevice tl > nodevice tx > nodevice vge > nodevice vr > nodevice wb > nodevice xl > nodevice cs > nodevice ed > nodevice ex > nodevice ep > nodevice fe > nodevice sn > nodevice xe > nodevice wlan > nooptions IEEE80211_DEBUG > nooptions IEEE80211_AMPDU_AGE > nooptions IEEE80211_SUPPORT_MESH > nodevice wlan_wep > nodevice wlan_ccmp > nodevice wlan_tkip > nodevice wlan_amrr > nodevice an > nodevice ath > nodevice ath_pci > nodevice ath_hal > nooptions AH_SUPPORT_AR5416 > nodevice ath_rate_sample > nodevice ipw > nodevice iwi > nodevice iwn > nodevice malo > nodevice mwl > nodevice ral > nodevice wi > nodevice wpi > nodevice md > nooption USB_DEBUG > nodevice uhci > nodevice ohci > nodevice ehci > nodevice xhci > nodevice usb > nodevice uhid > nodevice ukbd > nodevice ulpt > nodevice umass > nodevice ums > nodevice urio > nodevice u3g > nodevice uark > nodevice ubsa > nodevice uftdi > nodevice uipaq > nodevice uplcom > nodevice uslcom > nodevice uvisor > nodevice uvscom > nodevice aue > nodevice axe > nodevice cdce > nodevice cue > nodevice kue > nodevice rue > nodevice udav > nodevice rum > nodevice run > nodevice uath > nodevice upgt > nodevice ural > nodevice urtw > nodevice zyd > #nodevice firewire > nodevice fwe > nodevice fwip > #nodevice dcons > #nodevice dcons_rom > nodevice sound > nodevice snd_es137x > nodevice snd_hda > nodevice snd_ich > nodevice snd_uaudio > nodevice snd_via8233 > > World was also rebuilt as recommended by the handbook. As you can see I > was rebuilding for IPSEC (for testing purposes only note). I couldn't > remove dcons (not sure why- missing defined references), and that pulled > in firewire too. > > The result was surprising: a 14M kernel became 6.3M, and when running I > found it only used 19M used for wired (whoopee!) as opposed to 35M. No > services were running per se, only the usual suspects in base: > > vpn-test# ps ax > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.11 [kernel] > 1 ?? ILs 0:00.01 /sbin/init -- > 2 ?? DL 0:00.00 [crypto] > 3 ?? DL 0:00.00 [crypto returns] > 4 ?? DL 0:00.00 [sctp_iterator] > 5 ?? DL 0:00.00 [xpt_thrd] > 6 ?? DL 0:00.10 [pagedaemon] > 7 ?? DL 0:00.00 [vmdaemon] > 8 ?? DL 0:00.01 [pagezero] > 9 ?? DL 0:00.30 [bufdaemon] > 10 ?? DL 0:00.00 [audit] > 11 ?? RL 589:34.00 [idle] > 12 ?? WL 0:38.64 [intr] > 13 ?? DL 0:12.21 [geom] > 14 ?? DL 0:03.30 [yarrow] > 15 ?? DL 0:04.40 [syncer] > 16 ?? DL 0:00.63 [vnlru] > 17 ?? DL 0:00.53 [softdepflush] > 104 ?? Is 0:00.00 adjkerntz -i > 582 ?? Is 0:00.00 /sbin/devd > 737 ?? Ss 0:00.09 /usr/sbin/syslogd -s > 912 ?? Ss 0:02.68 /usr/sbin/ntpd -c /etc/ntp.conf -p > /var/run/ntpd.pid > 977 ?? Is 0:00.00 /usr/sbin/sshd > 984 ?? Ss 0:00.81 sendmail: accepting connections (sendmail) > 988 ?? Is 0:00.01 sendmail: Queue runner@00:30:00 for > /var/spool/client > 994 ?? Ss 0:00.12 /usr/sbin/cron -s > 2061 ?? Is 0:00.03 sshd: admin [priv] (sshd) > 2064 ?? S 0:00.04 sshd: admin@pts/0 (sshd) > 1052 v0 Is 0:00.01 login [pam] (login) > 1060 v0 I+ 0:00.02 -csh (csh) > 1053 v1 Is+ 0:00.00 /usr/libexec/getty Pc ttyv1 > 1054 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2 > 1055 v3 Is+ 0:00.00 /usr/libexec/getty Pc ttyv3 > 1056 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4 > 1057 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5 > 1058 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6 > 1059 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7 > 2065 0 Is 0:00.02 -csh (csh) > 2068 0 I 0:00.01 su > 2069 0 S 0:00.04 _su (csh) > 2414 0 R+ 0:00.00 ps ax > > After some minutes though, the usage went up to 39M. WTF? > > So I'm now thoroughly confused. Google didn't really show up any real > answers either. Aside from discovering the true nature of what was > discussed in the posts, my hypothetical theorising is for my own > academics as well; and I'm trying to slim down my kernels to see if I > can improve performance with low memory systems. > > Can process structures cause this much ballooning? I find that hard to > believe given not much is running here. My only other thought would be > pipe or network structures? Anything I'm missing? > > FWIW, my trimmed down, slim and slender, aerodynamic kernel can boot in > seconds as opposed to minutes. Sweet! Although compiling clang took > years... and gcc was built as well :/ > > Cheers > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 12 23:23:43 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 82DCF1065670 for ; Mon, 12 Mar 2012 23:23:43 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 100C18FC12 for ; Mon, 12 Mar 2012 23:23:42 +0000 (UTC) Received: by wibhq7 with SMTP id hq7so3710316wib.13 for ; Mon, 12 Mar 2012 16:23:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GRZAXZu85K65zHkn8pYqKTVUketC1c8N7zGCNbghfP8=; b=R6LIDZEDyCcYks0f3KFaLlItRsZfw9qx5lFiVseFMk13jLdT/ldmTZ0Azwvlbf21VL EGKp2nbDtzLeWSjm2ZpwOzbMQ9q2bxuU7ooT9c4qboKlzFPDjR8leulbzHgIeuee9Emd Y7ASxtwIvl0jUr7+2fyAktdY9T9n9uQu7X3YK58GUfO5nKprOPuFejf/DI39Y0wDRLsV XZX3pMYAJN3iiWXIyGcz9Z9KMvfUZ0t5qkZobAUMv4nN7elyb66zSUgc9vKVI7NbfxgD wQ1YzGOhInfwLyDfQ4zxjlAJ+EVcPj/1p8kJlCExnebS1YlOndfxsCpsUZo+ImWyr/Z8 XZSw== MIME-Version: 1.0 Received: by 10.180.91.10 with SMTP id ca10mr1950191wib.17.1331594622001; Mon, 12 Mar 2012 16:23:42 -0700 (PDT) Received: by 10.180.75.41 with HTTP; Mon, 12 Mar 2012 16:23:41 -0700 (PDT) In-Reply-To: References: Date: Mon, 12 Mar 2012 19:23:41 -0400 Message-ID: From: Ryan Stone To: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: hack.So: could not read symbols X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 23:23:43 -0000 2012/3/12 Fernando Apestegu=EDa : > I'm using 9.0-RELEASE. > > I downloaded the snapshot "9.0-CURRENT-201012" and tried to build it's > kernel but I get this error: > > hack.So: could not read symbols: File in wrong format > > file reports this: > > ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically > linked, not stripped > > I compared this file with the same file generated during the > compilation of the 9.0-RELEASE GENERIC kernel and they are identical. > > What's the problem here? I saw a similar issue trying to build a stable/8 kernel on 9.0-RELEASE. Doing a make kernel-toolchain before make buildkernel fixed the issue. From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 13 11:22:43 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 92F361065670 for ; Tue, 13 Mar 2012 11:22:43 +0000 (UTC) (envelope-from freebsd-hackers@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id DC4668FC14 for ; Tue, 13 Mar 2012 11:22:42 +0000 (UTC) Received: from mail.unitedinsong.com.au (bell.herveybayaustralia.com.au [192.168.0.40]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 8B6135C28 for ; Tue, 13 Mar 2012 21:36:13 +1000 (EST) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 333D55C22 for ; Tue, 13 Mar 2012 21:36:13 +1000 (EST) Message-ID: <4F5F2CC5.80608@herveybayaustralia.com.au> Date: Tue, 13 Mar 2012 21:17:25 +1000 From: Da Rock <9Phackers@herveybayaustralia.com.au> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4F5D48E6.9010802@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 13 Mar 2012 12:09:54 +0000 Subject: Re: Kernel memory usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 11:22:43 -0000 On 03/13/12 05:40, Super Bisquit wrote: > CPU architecture and model have a lot to do with performance. > You will also get different results if you used qemu in place of > VirtualBox. Qemu allows you to choose different emulated > architectures, CPUs, and machine bases. What's the downside? You have > to use the command line. > Install qemu and run a series of virtual machines. > Embedded devices also include Power(PC), ARMv?, Coldfire, et al; > you're only dealing with i386 and/or the 64 bit extension (AMD64). > CISC- which does not contain any hardware modification to be a RISC > replacement- runs fewer instructions than RISC due to the limited > number of registers. Take this into consideration every time a > program runs. > Everything else also matters on real and emulated systems: > Is it ide, scsi, sdd, flashdevice for the hard drive? > What type of RAM? > Dedicated or shared disk? I'm a little confused by the response, I was interested if someone knew what determines the size of kernel in memory (or wired); I only considered the embedded list because they have a greater interest in the memory size working with so little. It is academic as I'm trying to understand the kernel internals, as well as understand what works with low memory so I can tune accordingly. I understand the different CPU instruction sets (roughly), although I would be interested as to the size of the kernel in each. What my question was about was the wired memory size and what makes it grow (to put it super simply :) ). I know some growth would be expected, but this seems obese; how would I find out how much memory a process structure takes? Or else what am I missing? That said I'll have a crack at what you suggest as that follows a whole new interesting tangent :) I have used qemu before, but found VBox a bit more responsive (and, I will admit, easier...) > > On 3/11/12, Da Rock<9Phackers@herveybayaustralia.com.au> wrote: >> I may be required to move this to embedded, but I am only looking for >> generalisation. >> >> Recently a thread came up on questions regarding memory usage, and a >> post was made regarding wired memory being nearly all kernel- something >> I was ready to dispute, but then I thought I'd better make sure. >> >> So I tested a few theories first off: >> >> 1. Comparing memory usage across machines >> >> I checked servers and desktops as well as vm's for memory usage, and I >> found some interesting results. On a firewall with no apps installed >> only 35M wired is used, on a desktop up to 700M~ can be used. Even as a >> dedicated server with a few services used it remains around 35M. >> >> Surely this means that the wired memory used is not just kernel? But I >> held off my assumptions as it was still plausible that the structures >> used by the kernel could balloon that far, too. >> >> 2. Stripped down, lean mean, kernel machine >> >> I then (using a vm I was building a kernel for anyway) stripped down a >> kernel in a VBox VM using le drivers for network to see what could be >> achieved. This is my kernel conf: >> >> include GENERIC >> ident VPN >> options IPSEC >> options IPSEC_DEBUG >> options IPSEC_NAT_T >> device crypto >> device enc >> >> # minimise kernel >> nooptions UFS_GJOURNAL >> nooptions MD_ROOT >> nooptions NFSCL >> nooptions NFSD >> nooptions NFSLOCKD >> nooptions NFS_ROOT >> nooptions MSDOSFS >> nooptions CD9660 >> nooptions PROCFS >> nooptions PSEUDOFS >> nodevice fdc >> nodevice mvs >> nodevice siis >> nodevice ahc >> nodevice ahd >> nodevice esp >> nodevice hptiop >> nodevice isp >> nodevice mpt >> nodevice mps >> nodevice sym >> nodevice trm >> nodevice adv >> nodevice adw >> nodevice aic >> nodevice bt >> nodevice ses >> nodevice amr >> nodevice arcmsr >> nodevice ciss >> nodevice dpt >> nodevice hptmv >> nodevice hptrr >> nodevice irr >> nodevice ips >> nodevice mly >> nodevice twa >> nodevice aac >> nodevice aacp >> nodevice ida >> nodevice mfi >> nodevice mlx >> nodevice twe >> nodevice tws >> nodevice splash >> nodevice cbb >> nodevice pccard >> nodevice cardbus >> nodevice uart >> nodevice ppc >> nodevice ppbus >> nodevice lpt >> nodevice plip >> nodevice ppi >> nodevice puc >> nodevice bxe >> nodevice de >> nodevice em >> nodevice igb >> nodevice ixgbe >> nodevice ti >> nodevice txp >> nodevice vx >> nodevice miibus >> nodevice ae >> nodevice age >> nodevice alc >> nodevice ale >> nodevice bce >> nodevice bfe >> nodevice bge >> nodevice dc >> nodevice et >> nodevice fxp >> nodevice jme >> nodevice lge >> nodevice msk >> nodevice nfe >> nodevice nge >> nodevice pcn >> nodevice re >> nodevice rl >> nodevice sf >> nodevice sge >> nodevice sis >> nodevice sk >> nodevice ste >> nodevice stge >> nodevice tl >> nodevice tx >> nodevice vge >> nodevice vr >> nodevice wb >> nodevice xl >> nodevice cs >> nodevice ed >> nodevice ex >> nodevice ep >> nodevice fe >> nodevice sn >> nodevice xe >> nodevice wlan >> nooptions IEEE80211_DEBUG >> nooptions IEEE80211_AMPDU_AGE >> nooptions IEEE80211_SUPPORT_MESH >> nodevice wlan_wep >> nodevice wlan_ccmp >> nodevice wlan_tkip >> nodevice wlan_amrr >> nodevice an >> nodevice ath >> nodevice ath_pci >> nodevice ath_hal >> nooptions AH_SUPPORT_AR5416 >> nodevice ath_rate_sample >> nodevice ipw >> nodevice iwi >> nodevice iwn >> nodevice malo >> nodevice mwl >> nodevice ral >> nodevice wi >> nodevice wpi >> nodevice md >> nooption USB_DEBUG >> nodevice uhci >> nodevice ohci >> nodevice ehci >> nodevice xhci >> nodevice usb >> nodevice uhid >> nodevice ukbd >> nodevice ulpt >> nodevice umass >> nodevice ums >> nodevice urio >> nodevice u3g >> nodevice uark >> nodevice ubsa >> nodevice uftdi >> nodevice uipaq >> nodevice uplcom >> nodevice uslcom >> nodevice uvisor >> nodevice uvscom >> nodevice aue >> nodevice axe >> nodevice cdce >> nodevice cue >> nodevice kue >> nodevice rue >> nodevice udav >> nodevice rum >> nodevice run >> nodevice uath >> nodevice upgt >> nodevice ural >> nodevice urtw >> nodevice zyd >> #nodevice firewire >> nodevice fwe >> nodevice fwip >> #nodevice dcons >> #nodevice dcons_rom >> nodevice sound >> nodevice snd_es137x >> nodevice snd_hda >> nodevice snd_ich >> nodevice snd_uaudio >> nodevice snd_via8233 >> >> World was also rebuilt as recommended by the handbook. As you can see I >> was rebuilding for IPSEC (for testing purposes only note). I couldn't >> remove dcons (not sure why- missing defined references), and that pulled >> in firewire too. >> >> The result was surprising: a 14M kernel became 6.3M, and when running I >> found it only used 19M used for wired (whoopee!) as opposed to 35M. No >> services were running per se, only the usual suspects in base: >> >> vpn-test# ps ax >> PID TT STAT TIME COMMAND >> 0 ?? DLs 0:00.11 [kernel] >> 1 ?? ILs 0:00.01 /sbin/init -- >> 2 ?? DL 0:00.00 [crypto] >> 3 ?? DL 0:00.00 [crypto returns] >> 4 ?? DL 0:00.00 [sctp_iterator] >> 5 ?? DL 0:00.00 [xpt_thrd] >> 6 ?? DL 0:00.10 [pagedaemon] >> 7 ?? DL 0:00.00 [vmdaemon] >> 8 ?? DL 0:00.01 [pagezero] >> 9 ?? DL 0:00.30 [bufdaemon] >> 10 ?? DL 0:00.00 [audit] >> 11 ?? RL 589:34.00 [idle] >> 12 ?? WL 0:38.64 [intr] >> 13 ?? DL 0:12.21 [geom] >> 14 ?? DL 0:03.30 [yarrow] >> 15 ?? DL 0:04.40 [syncer] >> 16 ?? DL 0:00.63 [vnlru] >> 17 ?? DL 0:00.53 [softdepflush] >> 104 ?? Is 0:00.00 adjkerntz -i >> 582 ?? Is 0:00.00 /sbin/devd >> 737 ?? Ss 0:00.09 /usr/sbin/syslogd -s >> 912 ?? Ss 0:02.68 /usr/sbin/ntpd -c /etc/ntp.conf -p >> /var/run/ntpd.pid >> 977 ?? Is 0:00.00 /usr/sbin/sshd >> 984 ?? Ss 0:00.81 sendmail: accepting connections (sendmail) >> 988 ?? Is 0:00.01 sendmail: Queue runner@00:30:00 for >> /var/spool/client >> 994 ?? Ss 0:00.12 /usr/sbin/cron -s >> 2061 ?? Is 0:00.03 sshd: admin [priv] (sshd) >> 2064 ?? S 0:00.04 sshd: admin@pts/0 (sshd) >> 1052 v0 Is 0:00.01 login [pam] (login) >> 1060 v0 I+ 0:00.02 -csh (csh) >> 1053 v1 Is+ 0:00.00 /usr/libexec/getty Pc ttyv1 >> 1054 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2 >> 1055 v3 Is+ 0:00.00 /usr/libexec/getty Pc ttyv3 >> 1056 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4 >> 1057 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5 >> 1058 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6 >> 1059 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7 >> 2065 0 Is 0:00.02 -csh (csh) >> 2068 0 I 0:00.01 su >> 2069 0 S 0:00.04 _su (csh) >> 2414 0 R+ 0:00.00 ps ax >> >> After some minutes though, the usage went up to 39M. WTF? >> >> So I'm now thoroughly confused. Google didn't really show up any real >> answers either. Aside from discovering the true nature of what was >> discussed in the posts, my hypothetical theorising is for my own >> academics as well; and I'm trying to slim down my kernels to see if I >> can improve performance with low memory systems. >> >> Can process structures cause this much ballooning? I find that hard to >> believe given not much is running here. My only other thought would be >> pipe or network structures? Anything I'm missing? >> >> FWIW, my trimmed down, slim and slender, aerodynamic kernel can boot in >> seconds as opposed to minutes. Sweet! Although compiling clang took >> years... and gcc was built as well :/ >> >> Cheers >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 13 12:54:39 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 348941065670 for ; Tue, 13 Mar 2012 12:54:39 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id E57638FC12 for ; Tue, 13 Mar 2012 12:54:38 +0000 (UTC) Received: by yhgm50 with SMTP id m50so634011yhg.13 for ; Tue, 13 Mar 2012 05:54:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Dj+vW6DuqOxtVLMaVdNZIWtM3Su+sx7jjDbElP233zs=; b=rPcDU8ms42djc3HePGxp7U7JNfueeKWCZ+r29z1+Mx0cOIBLuIawgNsKasCxWSTkHn zK5gS+YbcIJuw4fYxwQ/TOtM7HbIkcApwbh0sbG/C1qlpDNE0BVZ6BuLTbhsHFdN5AU+ T7uFIj0DRO1nCQHMIuOgbEMdnBRfjAjUIb09RDs7PYrqzj7fUrustDN5u09SYo52JLu+ KRblq5X6q59v/i6n0Ynlryt7Z2pKtKaUN2Ciyir74eS+I/ZwpYVxswgEJrSlkBAm7LKA kP59KLn9KBnwd0qMpZ0OynoHrbZdz0I5s1WmHVhboyd7ldNky5+nJcGapDlrECENeyUD JvyQ== MIME-Version: 1.0 Received: by 10.236.154.168 with SMTP id h28mr16915474yhk.59.1331643278289; Tue, 13 Mar 2012 05:54:38 -0700 (PDT) Received: by 10.236.75.162 with HTTP; Tue, 13 Mar 2012 05:54:38 -0700 (PDT) In-Reply-To: <20120312181921.GF75778@deviant.kiev.zoral.com.ua> References: <20120312181921.GF75778@deviant.kiev.zoral.com.ua> Date: Tue, 13 Mar 2012 13:54:38 +0100 Message-ID: From: Svatopluk Kraus To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org Subject: Re: [vfs] buf_daemon() slows down write() severely on low-speed CPU X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 12:54:39 -0000 On Mon, Mar 12, 2012 at 7:19 PM, Konstantin Belousov wrote: > On Mon, Mar 12, 2012 at 04:00:58PM +0100, Svatopluk Kraus wrote: >> Hi, >> >> =A0 =A0I have solved a following problem. If a big file (according to >> 'hidirtybuffers') is being written, the write speed is very poor. >> >> =A0 =A0It's observed on system with elan 486 and 32MB RAM (i.e., low spe= ed >> CPU and not too much memory) running FreeBSD-9. >> >> =A0 =A0Analysis: A file is being written. All or almost all dirty buffer= s >> belong to the file. The file vnode is almost all time locked by >> writing process. The buf_daemon() can not flush any dirty buffer as a >> chance to acquire the file vnode lock is very low. A number of dirty >> buffers grows up very slow and with each new dirty buffer slower, >> because buf_daemon() eats more and more CPU time by looping on dirty >> buffers queue (with very low or no effect). >> >> =A0 =A0This slowing down effect is started by buf_daemon() itself, when >> 'numdirtybuffers' reaches 'lodirtybuffers' threshold and buf_daemon() >> is waked up by own timeout. The timeout fires at 'hz' period, but >> starts to fire at 'hz/10' immediately as buf_daemon() fails to reach >> 'lodirtybuffers' threshold. When 'numdirtybuffers' (now slowly) >> reaches ((lodirtybuffers + hidirtybuffers) / 2) threshold, the >> buf_daemon() can be waked up within bdwrite() too and it's much worse. >> Finally and with very slow speed, the 'hidirtybuffers' or >> 'dirtybufthresh' is reached, the dirty buffers are flushed, and >> everything starts from beginning... > Note that for some time, bufdaemon work is distributed among bufdaemon > thread itself and any thread that fails to allocate a buffer, esp. > a thread that owns vnode lock and covers long queue of dirty buffers. However, the problem starts when numdirtybuffers reaches lodirtybuffers count and ends around hidirtybuffers count. There are still plenty of free buffers in system. >> >> =A0 =A0On the system, a buffer size is 512 bytes and the default >> thresholds are following: >> >> =A0 =A0vfs.hidirtybuffers =3D 134 >> =A0 =A0vfs.lodirtybuffers =3D 67 >> =A0 =A0vfs.dirtybufthresh =3D 120 >> >> =A0 =A0For example, a 2MB file is copied into flash disk in about 3 >> minutes and 15 second. If dirtybufthresh is set to 40, the copy time >> is about 20 seconds. >> >> =A0 =A0My solution is a mix of three things: >> =A0 =A01. Suppresion of buf_daemon() wakeup by setting bd_request to 1 i= n >> the main buf_daemon() loop. > I cannot understand this. Please provide a patch that shows what do > you mean there. > curthread->td_pflags |=3D TDP_NORUNNINGBUF | TDP_BUFNEED; mtx_lock(&bdlock); for (;;) { - bd_request =3D 0; + bd_request =3D 1; mtx_unlock(&bdlock); I read description of bd_request variable. However, bd_request should serve as an indicator that buf_daemon() is in sleep. I.e., the following paradigma should be used: mtx_lock(&bdlock); bd_request =3D 0; /* now, it's only time when wakeup() will be meaningfu= l */ sleep(&bd_request, ..., hz/10); bd_request =3D 1; /* in case of timeout, we must set it (bd_wakeup() already set it) */ mtx_unlock(&bdlock); My patch follows the paradigma. What happens without the patch in described problem: buf_daemon() fails in its job and goes to sleep with hz/10 period. It supposes that next early wakeup will do nothing too. bd_request is untouched but buf_daemon() doesn't know if its last wakeup was made by bd_wakeup() or by timeout. So, bd_request could be 0 and buf_daemon() can be waked up before hz/10 just by bd_wakeup(). Moreover, setting bd_request to 0 when buf_daemon() is not in sleep can cause time consuming and useless wakeup() calls without effect. >> =A0 =A02. Increment of buf_daemon() fast timeout from hz/10 to hz/4. >> =A0 =A03. Tuning dirtybufthresh to (((lodirtybuffers + hidirtybuffers) / >> 2) - 15) magic. > Even hz / 10 is awfully long time on modern hardware. > The dirtybufthresh is already the sysctl that you can change. Yes, I noted low-speed CPU. Don't forget that even if buf_daemon() sleeps for hz/4 period (and this is expected to be rare case), dirtybufthresh still works and helps. And I don't push the changes (except bd_request one (a little)). I'm just sharing my experience. > The 32MB is indeed around the lowest amount of memory where recent > FreeBSD can make an illusion of being useful. I am not sure how much > should the system be tuned by default for such configuration. Even recent FreeBSD on this configuration is useful pretty much. Of course, file operations are not main concern ... IMHO, it's always good to know how the system works (and its parts) in various configurations. >> >> =A0 =A0The mention copy time is about 30 seconds now. >> >> =A0 =A0The described problem is just for information to anyone who can b= e >> interested in. Comments are welcome. However, the bd_request thing is >> more general. >> >> =A0 =A0bd_request (despite its description) should be 0 only when >> buf_daemon() is in sleep(). Otherwise, wakeup() on &bd_request channel >> is useless. Therefore, setting bd_request to 1 in the main >> buf_daemon() loop is correct and better as it saves time spent by >> wakeup() on not existing channel. Thanks for your comments, Svata From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 13 20:27:05 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7B4C106566B for ; Tue, 13 Mar 2012 20:27:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 841D18FC0C for ; Tue, 13 Mar 2012 20:27:05 +0000 (UTC) Received: by yenl9 with SMTP id l9so1244590yen.13 for ; Tue, 13 Mar 2012 13:27:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=77+8EQ8aMw7rbXimvn+B4X6Xak80YXZY6VbNAVEjQjY=; b=T42wBPUZNWV2+3K8o5ISs/BjI1BF/F6olO3Q3HCpsdP1gnAP3Z4+q1Pp+rUg7P9ehD cmcBrxmb716zVfNNmebU5zzzVS1h2iOY2X5eq++gQAlMTwTonGtspBtlEkKl8sJ5OzvQ Yp2ZVgbkEWkK6ctPsB1/T8wkftnKFqFmyVerkyGVuTf2RZdH+SjPsm+NwnUWg6cYfTvS I10JnjT+d63A5EUFlEf9bXTrQJWfvAjkMiEuLyX8H9ehTfnfujRzLxejZGNsRAW+ns/H SD964HsI/hBJwpixuDqbZphQU66fY6JlEJYJAwAT32trQ8SBlZ1wy8eWWHsZui+CJbuj YkGw== MIME-Version: 1.0 Received: by 10.68.232.2 with SMTP id tk2mr182354pbc.68.1331670424418; Tue, 13 Mar 2012 13:27:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.33.5 with HTTP; Tue, 13 Mar 2012 13:27:04 -0700 (PDT) In-Reply-To: <20120312181921.GF75778@deviant.kiev.zoral.com.ua> References: <20120312181921.GF75778@deviant.kiev.zoral.com.ua> Date: Tue, 13 Mar 2012 13:27:04 -0700 X-Google-Sender-Auth: fQjw_tLOL-qsL69M4QlGDO_FZ6E Message-ID: From: Adrian Chadd To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: hackers@freebsd.org, Svatopluk Kraus Subject: Re: [vfs] buf_daemon() slows down write() severely on low-speed CPU X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 20:27:05 -0000 On 12 March 2012 11:19, Konstantin Belousov wrote: > The 32MB is indeed around the lowest amount of memory where recent > FreeBSD can make an illusion of being useful. I am not sure how much > should the system be tuned by default for such configuration. Some -new- embedded wifi hardware is shipping with 16MB of RAM. Just saying, Adrian From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 13 20:50:43 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 62D2B1065673 for ; Tue, 13 Mar 2012 20:50:42 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 5A4148FC14 for ; Tue, 13 Mar 2012 20:50:42 +0000 (UTC) Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id q2DKXCS2081287 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 13 Mar 2012 13:33:15 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4F5FAF1B.1080102@freebsd.org> Date: Tue, 13 Mar 2012 13:33:31 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19 MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: will 9.2 be called 'diehard'? or maybe Naktomi? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 20:50:43 -0000 http://modcult.org/read/2008/2/20/nakatomi-socrates-bsd-9-2 From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 13 21:34:16 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 934C81065686 for ; Tue, 13 Mar 2012 21:34:16 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 136308FC14 for ; Tue, 13 Mar 2012 21:34:15 +0000 (UTC) Received: by lagv3 with SMTP id v3so1274924lag.13 for ; Tue, 13 Mar 2012 14:34:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=aYqfvRQkP5bvD+YOysUcLdcexOTfB9jflBAr6Xs/6SU=; b=BUc/4eYNoF49HFbuxOjxxgWIcjCwmlG5djZDE5lMQwygO2nMnnv1Hp9ZvLMmBo1u2B RXnZgggw3rCGhWzIbVlVWdxId16d6JUmrOOOUrUnAlH0LuPxfSOICmB7ziuwYcnly8nD J6NZ9x1CWSdpegyZ3meK4T2mPQBPrSubEcuNTQx8RgcuOXtWkKGq2Rde7ehib4TbyANC tvysf6YZU8dXXilIH0QQTxUcUyM00CRLx/p6mQ97X3yrIYnjHBzssyZPQy7JA1cM4Ijr Oj0R/3SS8yMWxw44iUUfsoruArVyEL8AzhuXtVkOA4AFEbYxXn+PJv2ICg+jsYRlwFAQ vu0w== MIME-Version: 1.0 Received: by 10.152.105.241 with SMTP id gp17mr131161lab.21.1331674448583; Tue, 13 Mar 2012 14:34:08 -0700 (PDT) Received: by 10.152.13.72 with HTTP; Tue, 13 Mar 2012 14:34:08 -0700 (PDT) In-Reply-To: References: Date: Tue, 13 Mar 2012 22:34:08 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: hack.So: could not read symbols X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 21:34:16 -0000 On Tue, Mar 13, 2012 at 12:23 AM, Ryan Stone wrote: > 2012/3/12 Fernando Apestegu=EDa : >> I'm using 9.0-RELEASE. >> >> I downloaded the snapshot "9.0-CURRENT-201012" and tried to build it's >> kernel but I get this error: >> >> hack.So: could not read symbols: File in wrong format >> >> file reports this: >> >> ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically >> linked, not stripped >> >> I compared this file with the same file generated during the >> compilation of the 9.0-RELEASE GENERIC kernel and they are identical. >> >> What's the problem here? > > I saw a similar issue trying to build a stable/8 kernel on > 9.0-RELEASE. =A0Doing a make kernel-toolchain before make buildkernel > fixed the issue. Yep, that was it. Thank you! I was able to compile the kernel but it can not mount root fs. It reports error 19 (ENODEV). Weird. It tries to mount ada0p2 that is properly detected if I type "?" when I get the mount prompt. From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 00:05:45 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA4C21065672; Wed, 14 Mar 2012 00:05:45 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 7E8908FC08; Wed, 14 Mar 2012 00:05:45 +0000 (UTC) Received: by dadp14 with SMTP id p14so4210098dad.18 for ; Tue, 13 Mar 2012 17:05:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+zvj2DC03rM8elaMx6LzcPHWIjWtFHS57VtihIicarc=; b=MwH+jbzW/tXABnI5iMoVHpzXcC2Foe/X5eVn3vLdpgGoNmN5+l6rbQs4pbcm2qxKvC Nt7sgaHdeOf3qaFuE8+e5Z2w/rUXRnx1jHC6wyJM+tbZozVAkcIq0KVc3fWewZg22fkm HT6gh3Y5mwNnr5tXJ0x+A4TSvzj3ZjXoJryj0KX2VVaukv2cH4RSS9J7d0vczpr6SPYE gA7nPfY4g58hQgqXtoh/Tat65SsR8oXhZ4bRD8Js3ynAqzOr9umCAZVzbX/LgFxGg+To IWaAOl0GgoBfKsKiBygUXFCM2IdenHWCUnjp9q/kxibS3epzkKEZYx2JvqmANjYlI/Yt O9/A== MIME-Version: 1.0 Received: by 10.68.189.5 with SMTP id ge5mr883037pbc.50.1331683545116; Tue, 13 Mar 2012 17:05:45 -0700 (PDT) Received: by 10.68.208.168 with HTTP; Tue, 13 Mar 2012 17:05:45 -0700 (PDT) In-Reply-To: <4F5FAF1B.1080102@freebsd.org> References: <4F5FAF1B.1080102@freebsd.org> Date: Tue, 13 Mar 2012 20:05:45 -0400 Message-ID: From: Super Bisquit To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 Cc: hackers@freebsd.org Subject: Re: will 9.2 be called 'diehard'? or maybe Naktomi? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 00:05:45 -0000 "Energizer Bunny" is more threatening. On 3/13/12, Julian Elischer wrote: > > > http://modcult.org/read/2008/2/20/nakatomi-socrates-bsd-9-2 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 04:51:26 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 374D0106566B; Wed, 14 Mar 2012 04:51:26 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id D83118FC18; Wed, 14 Mar 2012 04:51:25 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa07 [127.0.0.1]) by ltcfislmsgpa07.fnfis.com (8.14.4/8.14.4) with SMTP id q2E3Qwsg018923; Tue, 13 Mar 2012 22:47:03 -0500 Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa07.fnfis.com with ESMTP id 13jh7hrbej-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 13 Mar 2012 22:47:03 -0500 Received: from [10.0.0.101] (10.14.152.61) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 13 Mar 2012 22:47:01 -0500 MIME-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset="us-ascii" From: Devin Teske In-Reply-To: <20120306091003.GA77008@freebsd.org> Date: Tue, 13 Mar 2012 20:47:00 -0700 Content-Transfer-Encoding: quoted-printable Message-ID: References: <0b7101ccfb32$58d459f0$0a7d0dd0$@fisglobal.com> <20120306091003.GA77008@freebsd.org> To: Alexander Best X-Mailer: Apple Mail (2.1257) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7498, 1.0.260, 0.0.0000 definitions=2012-03-14_02:2012-03-13, 2012-03-14, 1970-01-01 signatures=0 Cc: FreeBSD Hackers , Ron McDowell Subject: Re: [PREVIEW] bsdconfig(8) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 04:51:26 -0000 On Mar 6, 2012, at 1:10 AM, Alexander Best wrote: > great work. a few questions or rather suggestions: >=20 [snip] > 2) the highlighted first letters suggest that these are shortcuts. they w= ork > great for the actual menu items, but for "" and "", > pressing O and E doesn't work. in fact E is already taken by "Startup". It's since been discovered that --visit-items achieves the desired behavior= (and is accepted by Xdialog(1) so seems safe to use unconditionally). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 14:43:10 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8797A106564A; Wed, 14 Mar 2012 14:43:09 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3BD358FC14; Wed, 14 Mar 2012 14:43:09 +0000 (UTC) Received: from shiny-w0.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id q2EEh5ZG017110; Wed, 14 Mar 2012 09:43:06 -0500 (CDT) (envelope-from rcm@fuzzwad.org) Message-ID: <4F60AE79.4000208@fuzzwad.org> Date: Wed, 14 Mar 2012 09:43:05 -0500 From: Ron McDowell User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Devin Teske References: <0b7101ccfb32$58d459f0$0a7d0dd0$@fisglobal.com> <20120306091003.GA77008@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 14 Mar 2012 15:15:31 +0000 Cc: Alexander Best , FreeBSD Hackers Subject: Re: [PREVIEW] bsdconfig(8) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 14:43:10 -0000 On 3/13/12 10:47 PM, Devin Teske wrote: > On Mar 6, 2012, at 1:10 AM, Alexander Best wrote: > >> great work. a few questions or rather suggestions: >> > [snip] > >> 2) the highlighted first letters suggest that these are shortcuts. they work >> great for the actual menu items, but for "" and"", >> pressing O and E doesn't work. in fact E is already taken by "Startup". > It's since been discovered that --visit-items achieves the desired behavior (and is accepted by Xdialog(1) so seems safe to use unconditionally). Let me verify that --visit-items works with i18n as well. -- Ron McDowell San Antonio TX From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 16:32:04 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97AA81065670 for ; Wed, 14 Mar 2012 16:32:04 +0000 (UTC) (envelope-from maninya@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 58B278FC14 for ; Wed, 14 Mar 2012 16:32:04 +0000 (UTC) Received: by ggnk4 with SMTP id k4so2453559ggn.13 for ; Wed, 14 Mar 2012 09:31:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=aX4FyoUVRlosjuIJeUTGJaRz37i1wWYDIp1m6XZpTvE=; b=QmC/0+TCQtiWMFaUaH/W4/IYoHmaiGcF92AE/iKY8LmhF8EAZLC7rlsWDpNtw66rIe zrMVijqkkMk5k5wdjYjUSdJRgph5IUuIVFtthUs7ng43QwNi3PU+xzQJsYmhNu9Rw6Nw zpWSB/1sauQz08nXhWm+qNf84z2ltTl0C5NHgH9fZTHIll/69mdtWSoZyH2jkaFHIO7b wh7FLmXIYQcafnPd0nueT5/ZGDfINoAYRK9KTbqnHSJxvJxSHxiSTbUrzPFlBGQ981qb VYTr8kkhCffqEgcdpbJl3e1SvLgkqfxu0nDs4VHkyVY7qscTXkR5U1MMQ1XQW0i2mwqM 8RxQ== MIME-Version: 1.0 Received: by 10.236.124.3 with SMTP id w3mr3708443yhh.101.1331742717462; Wed, 14 Mar 2012 09:31:57 -0700 (PDT) Received: by 10.147.24.14 with HTTP; Wed, 14 Mar 2012 09:31:57 -0700 (PDT) Date: Wed, 14 Mar 2012 22:01:57 +0530 Message-ID: From: Maninya M To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Capture states of all processes at the same time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 16:32:04 -0000 How can I capture the states of all running processes at a particular point in time? How can I retrieve this information for later use? -- Maninya From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 17:19:17 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 383A2106566C for ; Wed, 14 Mar 2012 17:19:17 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id EA1378FC15 for ; Wed, 14 Mar 2012 17:19:16 +0000 (UTC) Received: by yenl9 with SMTP id l9so2510342yen.13 for ; Wed, 14 Mar 2012 10:19:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=FwI4IpA4lBvxvfZkqEy5GTrBrR7YmGE6J/8nBoGRvHI=; b=zo/lKgt1qILihH9YDN35OlAs58mGipU1BmAS7UH/G2l6x49BwEzLRrFwzlUUGkC0a+ zJbH+J8dkdwSK0lFrGvaKa9oC5mJLwIF+9LXy2eQEaMZm/dq7Ck7iYxXNar6AruztV/J 3qLbGzMBR0eJZFup7sMWy8GtjECQMuOHoWp1xwEZIyr9CpvSNx4qT4hchlW863QrDCDc 9eF4MaZNpXfJi5DUSfiwWhbNyFBM/bkzScdz/jwYzaxuNgLY+gV0GRhiDmb9fOB/P9LL f3MKKmxsHDlpQvhI7toMwJ6G6XzHtPNdNiCf6AYaDZCtlHj9kk36olMAbcUCx4pDdXis ENng== MIME-Version: 1.0 Received: by 10.236.78.40 with SMTP id f28mr3909050yhe.47.1331745554814; Wed, 14 Mar 2012 10:19:14 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.147.181.4 with HTTP; Wed, 14 Mar 2012 10:19:14 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Mar 2012 10:19:14 -0700 X-Google-Sender-Auth: Jj_73gY-ir_wYQ84F4IcEQFR96A Message-ID: From: Artem Belevich To: Maninya M Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Capture states of all processes at the same time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 17:19:17 -0000 On Wed, Mar 14, 2012 at 9:31 AM, Maninya M wrote: > How can I capture the states of all running processes at a particular point > in time? How can I retrieve this information for later use? Go into DDB. Do 'panic'. wait for the kernel to finish dumping core. Once system reboots and saves kernel core, examine process state in the core file with gdb. Obviously it's a postmortem examination which may not be exactly what you want. Less destructive option would be to do 'ps' or 'show threads' in DDB, save its output and then continue. --Artem From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 18:22:33 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5ED02106566C for ; Wed, 14 Mar 2012 18:22:33 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id D7B0E8FC0C for ; Wed, 14 Mar 2012 18:22:32 +0000 (UTC) Received: by lagv3 with SMTP id v3so2392732lag.13 for ; Wed, 14 Mar 2012 11:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=KGAwsPMr0Zxz/iKaubYtpo4qWq5hIpBH+6zboBUnYFo=; b=i6CEyel1rmb8heQFFPN6WYHt6dyXNtQ0uJIsNk4UCm0d1uFeWV2fav2lOUkL4AJPWz FfsfjtFcVuisaKBAnERwI1zlLgrXPYkiPaPbkRBFMN9Q2yUj0joaltYoBc88evha6MrB 9FPNXETsj5Tdh+gk9Alqc88zj0p+pTTlUL2n0omRRAGS3wZF8fOaS+GoC2D01mdpNpD1 dNLVVmKAMdiyqTSJhYI1yoZootqptphPRys91OyfJbDkhQqe8xBYD8uYZy7iTTLLdTtw BFNmO5Dn+IOf1K4GB2EjNXIEttWzErIH0xY4L/RNR8iM+Ul+C75rsNmVCggGlDJxOTqu KODg== MIME-Version: 1.0 Received: by 10.152.105.241 with SMTP id gp17mr2966193lab.21.1331749351768; Wed, 14 Mar 2012 11:22:31 -0700 (PDT) Received: by 10.152.13.72 with HTTP; Wed, 14 Mar 2012 11:22:31 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Mar 2012 19:22:31 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: hack.So: could not read symbols X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 18:22:33 -0000 On Tue, Mar 13, 2012 at 10:34 PM, Fernando Apestegu=EDa wrote: > On Tue, Mar 13, 2012 at 12:23 AM, Ryan Stone wrote: >> 2012/3/12 Fernando Apestegu=EDa : >>> I'm using 9.0-RELEASE. >>> >>> I downloaded the snapshot "9.0-CURRENT-201012" and tried to build it's >>> kernel but I get this error: >>> >>> hack.So: could not read symbols: File in wrong format >>> >>> file reports this: >>> >>> ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically >>> linked, not stripped >>> >>> I compared this file with the same file generated during the >>> compilation of the 9.0-RELEASE GENERIC kernel and they are identical. >>> >>> What's the problem here? >> >> I saw a similar issue trying to build a stable/8 kernel on >> 9.0-RELEASE. =A0Doing a make kernel-toolchain before make buildkernel >> fixed the issue. > > Yep, that was it. Thank you! > > I was able to compile the kernel but it can not mount root fs. It > reports error 19 (ENODEV). Weird. It tries to mount ada0p2 that is > properly detected if I type "?" when I get the mount prompt. Any idea why this happens? My filesystem is UFS + SUJ. I tried also with 9.0-RELEASE-201101 snapshot and it is unable to mount the root fs too. Thanks in advance. From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 18:25:43 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0134F1065679 for ; Wed, 14 Mar 2012 18:25:43 +0000 (UTC) (envelope-from maninya@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id B04D88FC14 for ; Wed, 14 Mar 2012 18:25:42 +0000 (UTC) Received: by yhgm50 with SMTP id m50so2587853yhg.13 for ; Wed, 14 Mar 2012 11:25:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HMT1BWjwVSfUpzBfA9GyRbCt9F7uzFd9DirhK/762y8=; b=Me1bCvGhj/kPyIAP3C5bkOXytiNTo6qYsMsC7EKAxqZnJo1WpBIdbJnHxo8D7padSU Sdi0TSxRmjMqlKoWPaR8ItfvMzRRHCzm4yz7izoX7MEF23WTTB9BgiJARgdeuL1z/wRr o6VomD8bJY7A5uhOUQT4DzX0+tVWhZjdRyXrPT1IYoy0hvcsezxpjiq6UXkd1p9Hq3yc YfV/xueB3P9f01NIJInXpPBj/Nz3ZmmtuGQxetQOWnOlFCiFh1JEZlpx5MBEDlx1NM2z f8txs3lSd/+/CB9J4Zhe0P9UEA3RnDN/l0Wb7nwOS4jwW10BC05ll5x9CwzmsaL+Vj4V 30OQ== MIME-Version: 1.0 Received: by 10.236.144.134 with SMTP id n6mr4337781yhj.50.1331749536695; Wed, 14 Mar 2012 11:25:36 -0700 (PDT) Received: by 10.147.24.14 with HTTP; Wed, 14 Mar 2012 11:25:36 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Mar 2012 23:55:36 +0530 Message-ID: From: Maninya M To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Capture states of all processes at the same time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 18:25:43 -0000 Thank you, I tried doing it the first way. I configured the kernel to include DDB, then typed on the console: sysctl debug.kdb.enter=1 to enter DDB. Then typed this to force a panic: sysctl debug.kdb.panic=1 The computer just hung after this, and after waiting for a while I pressed the reboot button. It said "no core dumps found" while rebooting. I couldn't find any core dumps in /var/crash either. So I tried again to enter DDB, typed sysctl debug.kdb.enter=1. Now the computer hangs even for this (tried it twice)! What did I do wrong? Please help me with the steps. On 14 March 2012 22:49, Artem Belevich wrote: > On Wed, Mar 14, 2012 at 9:31 AM, Maninya M wrote: > > How can I capture the states of all running processes at a particular > point > > in time? How can I retrieve this information for later use? > > Go into DDB. Do 'panic'. wait for the kernel to finish dumping core. > Once system reboots and saves kernel core, examine process state in > the core file with gdb. Obviously it's a postmortem examination which > may not be exactly what you want. > > Less destructive option would be to do 'ps' or 'show threads' in DDB, > save its output and then continue. > > --Artem > -- Maninya -- Maninya From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 19:08:02 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 401D9106564A for ; Wed, 14 Mar 2012 19:08:02 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id EE6908FC14 for ; Wed, 14 Mar 2012 19:08:01 +0000 (UTC) Received: by ggnk4 with SMTP id k4so2656040ggn.13 for ; Wed, 14 Mar 2012 12:08:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PqYfenaUXmuyLYC36ddgcS6TbUJPtmLF2U/KDGbPV50=; b=KEKIz1Gbofdk6q1k4gZqoTI1UyT9FNhi52znWA/MrV4dpvGCYqEUCOrWKEYBjjJlhT 6qPla98fqZnkG9ZAvz3sm6xxLkQg8C4MYqyGB5N+gq9w86doRVaje0846mt4Kn2rg8QY iMNm8yHtg7gwRGaLzHjnQTZkEt7nP81vG7w9dSXHem5nwzoYJktI3O+l2qCB6l2sgWLo sj0sIUs4VnfVw5jwqwRPbGTynTGjgd0VKRwQpdoCGozC1ni00g1RfYT2yyBo+EJa0VzH WOZOgkELI3MzYUspeJvrkexLkjqMt3HquiEAg3C0/bqaq0elsvhJjov5WpK+h5t1R7O8 55wg== MIME-Version: 1.0 Received: by 10.236.178.102 with SMTP id e66mr4510871yhm.30.1331751741987; Wed, 14 Mar 2012 12:02:21 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.147.181.4 with HTTP; Wed, 14 Mar 2012 12:02:21 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Mar 2012 12:02:21 -0700 X-Google-Sender-Auth: K1aq1z-AhA8AwCEpkReMbFTgdVQ Message-ID: From: Artem Belevich To: Maninya M Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Capture states of all processes at the same time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 19:08:02 -0000 On Wed, Mar 14, 2012 at 11:25 AM, Maninya M wrote: > Then typed this to force a panic: > > sysctl debug.kdb.panic=1 > > The computer just hung after this, and after waiting for a while I pressed > the reboot button. > It said "no core dumps found" while rebooting. First, make sure you have swap space configured. If minidump is not enabled (check sysctl debug.minidump) you will need to make sure you have more swap space than physical memory. Then make sure that dump device is set up correctly. See dumpdev in rc.conf(5) If that didn't work, you may be running into the issue in PR kern/155421: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F155421&cat= Alas, I don't know what to do about that. --Artem From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 14 20:27:04 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A878C106566B; Wed, 14 Mar 2012 20:27:04 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 7704A8FC15; Wed, 14 Mar 2012 20:27:04 +0000 (UTC) Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id q2EKR0uA088414 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Mar 2012 13:27:03 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4F60FF28.8010104@freebsd.org> Date: Wed, 14 Mar 2012 13:27:20 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19 MIME-Version: 1.0 To: Artem Belevich References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Maninya M , freebsd-hackers@freebsd.org Subject: Re: Capture states of all processes at the same time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 20:27:04 -0000 On 3/14/12 12:02 PM, Artem Belevich wrote: > On Wed, Mar 14, 2012 at 11:25 AM, Maninya M wrote: >> Then typed this to force a panic: >> >> sysctl debug.kdb.panic=1 >> >> The computer just hung after this, and after waiting for a while I pressed >> the reboot button. >> It said "no core dumps found" while rebooting. > First, make sure you have swap space configured. If minidump is not > enabled (check sysctl debug.minidump) you will need to make sure you > have more swap space than physical memory. > Then make sure that dump device is set up correctly. See dumpdev in rc.conf(5) > > If that didn't work, you may be running into the issue in PR kern/155421: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F155421&cat= > > Alas, I don't know what to do about that. or just do "ps" from ddb and then continue. you can set things up in 9 (and maybe 8, I don't know) to capture the ddb output.. > --Artem > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 15 11:30:07 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F886106566C for ; Thu, 15 Mar 2012 11:30:07 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 0F2128FC18 for ; Thu, 15 Mar 2012 11:30:06 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q2FBU0hG014142; Thu, 15 Mar 2012 13:30:00 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q2FBU0Ao005197; Thu, 15 Mar 2012 13:30:00 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q2FBTxnU005194; Thu, 15 Mar 2012 13:30:00 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 15 Mar 2012 13:29:59 +0200 From: Konstantin Belousov To: Svatopluk Kraus Message-ID: <20120315112959.GP75778@deviant.kiev.zoral.com.ua> References: <20120312181921.GF75778@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lcXxAbAqsng3jLE3" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: hackers@freebsd.org Subject: Re: [vfs] buf_daemon() slows down write() severely on low-speed CPU X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 11:30:07 -0000 --lcXxAbAqsng3jLE3 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 13, 2012 at 01:54:38PM +0100, Svatopluk Kraus wrote: > On Mon, Mar 12, 2012 at 7:19 PM, Konstantin Belousov > wrote: > > On Mon, Mar 12, 2012 at 04:00:58PM +0100, Svatopluk Kraus wrote: > >> Hi, > >> > >> =9A =9AI have solved a following problem. If a big file (according to > >> 'hidirtybuffers') is being written, the write speed is very poor. > >> > >> =9A =9AIt's observed on system with elan 486 and 32MB RAM (i.e., low s= peed > >> CPU and not too much memory) running FreeBSD-9. > >> > >> =9A =9AAnalysis: A file is being written. All or almost all dirty buff= ers > >> belong to the file. The file vnode is almost all time locked by > >> writing process. The buf_daemon() can not flush any dirty buffer as a > >> chance to acquire the file vnode lock is very low. A number of dirty > >> buffers grows up very slow and with each new dirty buffer slower, > >> because buf_daemon() eats more and more CPU time by looping on dirty > >> buffers queue (with very low or no effect). > >> > >> =9A =9AThis slowing down effect is started by buf_daemon() itself, when > >> 'numdirtybuffers' reaches 'lodirtybuffers' threshold and buf_daemon() > >> is waked up by own timeout. The timeout fires at 'hz' period, but > >> starts to fire at 'hz/10' immediately as buf_daemon() fails to reach > >> 'lodirtybuffers' threshold. When 'numdirtybuffers' (now slowly) > >> reaches ((lodirtybuffers + hidirtybuffers) / 2) threshold, the > >> buf_daemon() can be waked up within bdwrite() too and it's much worse. > >> Finally and with very slow speed, the 'hidirtybuffers' or > >> 'dirtybufthresh' is reached, the dirty buffers are flushed, and > >> everything starts from beginning... > > Note that for some time, bufdaemon work is distributed among bufdaemon > > thread itself and any thread that fails to allocate a buffer, esp. > > a thread that owns vnode lock and covers long queue of dirty buffers. >=20 > However, the problem starts when numdirtybuffers reaches > lodirtybuffers count and ends around hidirtybuffers count. There are > still plenty of free buffers in system. >=20 > >> > >> =9A =9AOn the system, a buffer size is 512 bytes and the default > >> thresholds are following: > >> > >> =9A =9Avfs.hidirtybuffers =3D 134 > >> =9A =9Avfs.lodirtybuffers =3D 67 > >> =9A =9Avfs.dirtybufthresh =3D 120 > >> > >> =9A =9AFor example, a 2MB file is copied into flash disk in about 3 > >> minutes and 15 second. If dirtybufthresh is set to 40, the copy time > >> is about 20 seconds. > >> > >> =9A =9AMy solution is a mix of three things: > >> =9A =9A1. Suppresion of buf_daemon() wakeup by setting bd_request to 1= in > >> the main buf_daemon() loop. > > I cannot understand this. Please provide a patch that shows what do > > you mean there. > > > curthread->td_pflags |=3D TDP_NORUNNINGBUF | TDP_BUFNEED; > mtx_lock(&bdlock); > for (;;) { > - bd_request =3D 0; > + bd_request =3D 1; > mtx_unlock(&bdlock); Is this a complete patch ? The change just causes lost wakeups for bufdaemo= n, nothing more. >=20 > I read description of bd_request variable. However, bd_request should > serve as an indicator that buf_daemon() is in sleep. I.e., the > following paradigma should be used: >=20 > mtx_lock(&bdlock); > bd_request =3D 0; /* now, it's only time when wakeup() will be meaning= ful */ > sleep(&bd_request, ..., hz/10); > bd_request =3D 1; /* in case of timeout, we must set it (bd_wakeup() > already set it) */ > mtx_unlock(&bdlock); >=20 > My patch follows the paradigma. What happens without the patch in > described problem: buf_daemon() fails in its job and goes to sleep > with hz/10 period. It supposes that next early wakeup will do nothing > too. bd_request is untouched but buf_daemon() doesn't know if its last > wakeup was made by bd_wakeup() or by timeout. So, bd_request could be > 0 and buf_daemon() can be waked up before hz/10 just by bd_wakeup(). > Moreover, setting bd_request to 0 when buf_daemon() is not in sleep > can cause time consuming and useless wakeup() calls without effect. --lcXxAbAqsng3jLE3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk9h0rcACgkQC3+MBN1Mb4g9ngCg8MORdNsQG98d+WPCrIAVEQUW Mk8AoKHzcO6cGDdJqE4SuW5cW7MUHGRb =wTjt -----END PGP SIGNATURE----- --lcXxAbAqsng3jLE3-- From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 15 11:23:35 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA39F106566C; Thu, 15 Mar 2012 11:23:35 +0000 (UTC) (envelope-from gnrp@komkon2.de) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.freebsd.org (Postfix) with ESMTP id 660538FC18; Thu, 15 Mar 2012 11:23:35 +0000 (UTC) X-Envelope-From: gnrp@komkon2.de Received: from adolfputzen (laptopecke.physik-pool.tu-berlin.de [130.149.58.159]) (authenticated bits=0) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id q2FBNRig024422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 15 Mar 2012 12:23:28 +0100 Date: Thu, 15 Mar 2012 12:23:19 +0100 From: Julian Djamil Fagir To: freebsd-hackers@freebsd.org Message-ID: <20120315122319.156ba444@adolfputzen> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.14.7; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/hZ.X.bflZ/QBtp69f=6j5cs"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 X-Mailman-Approved-At: Thu, 15 Mar 2012 12:15:02 +0000 Cc: Tom Rhodes Subject: Updating fscd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@freebsd.org, Julian Djamil Fagir List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 11:23:35 -0000 --Sig_/hZ.X.bflZ/QBtp69f=6j5cs Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, fscd by Tom Rhodes (see http://people.freebsd.org/~trhodes/fsc/) is a *very* nice tool for administrators, and I want to use it with our computers. But there were some usability flaws and he unfortunately didn't have time to continue working on it. These are my modifications, based on the last version he worked on: * there is a configuration file with one service per line, which should be monitored when starting up. * there is no database anymore, and no pidfiles being saved. You just need the service name (as processed by rc(8)), the rest will be fetched from rc(8)/service(8). * the whole startup of a service is now outsourced to service(8). We don't check pids anymore, we only ask service for the service's status and pids and then monitor these, the same after restarting. * several internal changes. The code from Tom Rhodes was nice, but when I worked on it it was easier for me to think of my own code structure instead of thinking into his ones. Anyway, most of his structure and code is still in it. * everything works and compiles in NetBSD. I'd like to see the service bei= ng named something more generic (bscd? ;), but I'm not the one to decide up= on the code of others. There were some minor incompatibilities, though nothing you couldn't fix in five minutes, I'd prefer having a single codebase instead of two diverging ones. To use it, you: * power up fscd with `fscd` (nothing more) * enable a service with `fscadm enable $SERVICE` * stop monitoring it with `fscadm disable $SERVICE` * show status with `fscadm status` * close fscd with `fscadm shutdown` (or kill[all]) You can also supply the option `-s` to fscd and fscadm to specify the socket to be used instead of the standard one (/var/run/fscd.sock). You can as well supply the option `-c` to fscd to specify the configuration file to be used instead of the standard one (/etc/fscd.conf). You can download it here: https://vcs.in-berlin.de/schrank21_fscd/ (Files->Version->Tarball) NOTE: The manpages are *out of date*, they will be updated soon. Any comments, questions, further change requests, etc.? If you think the changes are sane, I'll also update the manpages. Regards, Julian PS: Please include me in the replies, I'm not subscribed to this list. --Sig_/hZ.X.bflZ/QBtp69f=6j5cs Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAk9h0ScACgkQc7h7cu1Hpp63bQCfbuwwyABQy5y7rkdbOawheJju MOkAnRhhcISvwxHXjlHVlYYTfcs+OdY4 =WYjU -----END PGP SIGNATURE----- --Sig_/hZ.X.bflZ/QBtp69f=6j5cs-- From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 15 19:00:42 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3CD3E1065680 for ; Thu, 15 Mar 2012 19:00:42 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id E7F478FC0C for ; Thu, 15 Mar 2012 19:00:41 +0000 (UTC) Received: by ghrr20 with SMTP id r20so4129845ghr.13 for ; Thu, 15 Mar 2012 12:00:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rsE7EHMMoHNPIAPOySUpNzdTlM6sPWS8+dlD5IglgLc=; b=GRDrxdfTqlfvWO+F3w859wvifeIVnA5R1OmpqCZvBj4YziruyKhUICA4yrCN0ieLDa PXo1qDDsWRUMG8FSL4Ueg0O2SO6Uiyf3xVDSZSt6i1DVyRctIml7s5FzRGi0W46Qje+J XkOmNNuCzaCY/Unm/RosAoYqzdw0sCPSfJcN5cOOwZgS1E04MfVygOs5SqFT1/ul32wS D/LMv+Aj4DGvUYIntCZK5ZzuDuEjqk+fT6o7wLXj03YZSypqOPS4wDgf541DsO5Mwa5c UOfVZvW0buD7HlO6FAnvwRUVKRAoj5kMxt9UIagmJdhCh845Eexwuw74XUEWV3ddiuHW fXDA== MIME-Version: 1.0 Received: by 10.236.184.167 with SMTP id s27mr9845225yhm.8.1331838041241; Thu, 15 Mar 2012 12:00:41 -0700 (PDT) Received: by 10.236.75.162 with HTTP; Thu, 15 Mar 2012 12:00:41 -0700 (PDT) In-Reply-To: <20120315112959.GP75778@deviant.kiev.zoral.com.ua> References: <20120312181921.GF75778@deviant.kiev.zoral.com.ua> <20120315112959.GP75778@deviant.kiev.zoral.com.ua> Date: Thu, 15 Mar 2012 20:00:41 +0100 Message-ID: From: Svatopluk Kraus To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org Subject: Re: [vfs] buf_daemon() slows down write() severely on low-speed CPU X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 19:00:42 -0000 2012/3/15 Konstantin Belousov : > On Tue, Mar 13, 2012 at 01:54:38PM +0100, Svatopluk Kraus wrote: >> On Mon, Mar 12, 2012 at 7:19 PM, Konstantin Belousov >> wrote: >> > On Mon, Mar 12, 2012 at 04:00:58PM +0100, Svatopluk Kraus wrote: >> >> Hi, >> >> >> >> =A0 =A0I have solved a following problem. If a big file (according to >> >> 'hidirtybuffers') is being written, the write speed is very poor. >> >> >> >> =A0 =A0It's observed on system with elan 486 and 32MB RAM (i.e., low = speed >> >> CPU and not too much memory) running FreeBSD-9. >> >> >> >> =A0 =A0Analysis: A file is being written. All or almost all dirty buf= fers >> >> belong to the file. The file vnode is almost all time locked by >> >> writing process. The buf_daemon() can not flush any dirty buffer as a >> >> chance to acquire the file vnode lock is very low. A number of dirty >> >> buffers grows up very slow and with each new dirty buffer slower, >> >> because buf_daemon() eats more and more CPU time by looping on dirty >> >> buffers queue (with very low or no effect). >> >> >> >> =A0 =A0This slowing down effect is started by buf_daemon() itself, wh= en >> >> 'numdirtybuffers' reaches 'lodirtybuffers' threshold and buf_daemon() >> >> is waked up by own timeout. The timeout fires at 'hz' period, but >> >> starts to fire at 'hz/10' immediately as buf_daemon() fails to reach >> >> 'lodirtybuffers' threshold. When 'numdirtybuffers' (now slowly) >> >> reaches ((lodirtybuffers + hidirtybuffers) / 2) threshold, the >> >> buf_daemon() can be waked up within bdwrite() too and it's much worse= . >> >> Finally and with very slow speed, the 'hidirtybuffers' or >> >> 'dirtybufthresh' is reached, the dirty buffers are flushed, and >> >> everything starts from beginning... >> > Note that for some time, bufdaemon work is distributed among bufdaemon >> > thread itself and any thread that fails to allocate a buffer, esp. >> > a thread that owns vnode lock and covers long queue of dirty buffers. >> >> However, the problem starts when numdirtybuffers reaches >> lodirtybuffers count and ends around hidirtybuffers count. There are >> still plenty of free buffers in system. >> >> >> >> >> =A0 =A0On the system, a buffer size is 512 bytes and the default >> >> thresholds are following: >> >> >> >> =A0 =A0vfs.hidirtybuffers =3D 134 >> >> =A0 =A0vfs.lodirtybuffers =3D 67 >> >> =A0 =A0vfs.dirtybufthresh =3D 120 >> >> >> >> =A0 =A0For example, a 2MB file is copied into flash disk in about 3 >> >> minutes and 15 second. If dirtybufthresh is set to 40, the copy time >> >> is about 20 seconds. >> >> >> >> =A0 =A0My solution is a mix of three things: >> >> =A0 =A01. Suppresion of buf_daemon() wakeup by setting bd_request to = 1 in >> >> the main buf_daemon() loop. >> > I cannot understand this. Please provide a patch that shows what do >> > you mean there. >> > >> =A0 =A0 =A0 curthread->td_pflags |=3D TDP_NORUNNINGBUF | TDP_BUFNEED; >> =A0 =A0 =A0 mtx_lock(&bdlock); >> =A0 =A0 =A0 for (;;) { >> - =A0 =A0 =A0 =A0 =A0 =A0 bd_request =3D 0; >> + =A0 =A0 =A0 =A0 =A0 =A0 bd_request =3D 1; >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 mtx_unlock(&bdlock); > Is this a complete patch ? The change just causes lost wakeups for bufdae= mon, > nothing more. Yes, it's a complete patch. And exactly, it causes lost wakeups which are: 1. !! UNREASONABLE !!, because bufdaemon is not sleeping, 2. not wanted, because it looks that it's correct behaviour for the sleep with hz/10 period. However, if the sleep with hz/10 period is expected to be waked up by bd_wakeup(), then bd_request should be set to 0 just before sleep() call, and then bufdaemon behaviour will be clear. All stuff around bd_request and bufdaemon sleep is under bd_lock, so if bd_request is 0 and bufdaemon is not sleeping, then all wakeups are unreasonable! The patch is about that mainly. > >> >> I read description of bd_request variable. However, bd_request should >> serve as an indicator that buf_daemon() is in sleep. I.e., the >> following paradigma should be used: >> >> mtx_lock(&bdlock); >> bd_request =3D 0; =A0 =A0/* now, it's only time when wakeup() will be me= aningful */ >> sleep(&bd_request, ..., hz/10); >> bd_request =3D 1; =A0 /* in case of timeout, we must set it (bd_wakeup() >> already set it) */ >> mtx_unlock(&bdlock); >> >> My patch follows the paradigma. What happens without the patch in >> described problem: buf_daemon() fails in its job and goes to sleep >> with hz/10 period. It supposes that next early wakeup will do nothing >> too. bd_request is untouched but buf_daemon() doesn't know if its last >> wakeup was made by bd_wakeup() or by timeout. So, bd_request could be >> 0 and buf_daemon() can be waked up before hz/10 just by bd_wakeup(). >> Moreover, setting bd_request to 0 when buf_daemon() is not in sleep >> can cause time consuming and useless wakeup() calls without effect. From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 15 20:46:04 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C8B671065675 for ; Thu, 15 Mar 2012 20:46:04 +0000 (UTC) (envelope-from matthewstory@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8179B8FC0C for ; Thu, 15 Mar 2012 20:46:04 +0000 (UTC) Received: by vcmm1 with SMTP id m1so4928790vcm.13 for ; Thu, 15 Mar 2012 13:46:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=rocZSySyhh4V5YWTzSUCUhmclVj05TsC9vN4lLanssI=; b=pI6KvRv8EqOCGU2q3wzcr9LSGvjOAN7wu61afWXPc/VFd93DmMHoxqbgqTLPSfMnTa pWN/9txNkq8+qq6KBnFwBEmy70z/OPoE/DNu4L3mr5p7Iu1r2Lw1cs2aL8/KnlZkcGZ7 8vXD8glH0xEf1WwxeE8BErt+Hbb7c3lBSpB0SzbXO+DYtBaIuFlxtBTp63a8cLG6hC/L hFCsC6f3Jsa4NZXihxdMsLSxrSgGmdkfZdtsC1eWYb8IKKkRgpyRcZkl5hsDPyK8zCsP l+HnEdV7moe8uVjvgu6F7YpsWMGDlDdhjuxfQcpS+qX0XcjJQXeOqhea+vdVSw+hLPix AwxA== MIME-Version: 1.0 Received: by 10.52.28.228 with SMTP id e4mr48900vdh.57.1331844363511; Thu, 15 Mar 2012 13:46:03 -0700 (PDT) Received: by 10.52.93.42 with HTTP; Thu, 15 Mar 2012 13:46:03 -0700 (PDT) Date: Thu, 15 Mar 2012 16:46:03 -0400 Message-ID: From: Matthew Story To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FTSENT: name and path on `/' versus name and path on `*/' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 20:46:04 -0000 Found a curious incongruent behavior in fts(3), wondering if there is some reason for this, or if it's just a bug. If you include the path `/' the FTSENT at depth 0 that is returned for the path has both fts_path = "/" and fts_name = "/", compared to other entries, like /var which has fts_path = "/" and fts_path = "/" and fts_name = "var", or /var/, which has fts_path = "/var/" and fts_name = "". Given the behavior of other paths used in fts(3), my expectation here is that FTSENT for path "/" on depth 0 would have fts_path = "/" and fts_name = "". Haven't delved down into the code enough to figure out where this is happening, but from a cursory read through libc/gen/fts.c there doesn't seem to be any explicit special casing of the path "/". Can anyone shed light on why this behavior is desirable, or if it's just a bug I'm happy to file a PR and delve further into fts.c ... -- regards, matt From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 15 22:35:05 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 082921065672 for ; Thu, 15 Mar 2012 22:35:05 +0000 (UTC) (envelope-from jeremie@le-hen.org) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id 52F428FC0A for ; Thu, 15 Mar 2012 22:35:02 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id A789AD48028; Thu, 15 Mar 2012 23:34:56 +0100 (CET) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 732462675; Thu, 15 Mar 2012 22:34:55 +0000 (UTC) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 448E41942; Thu, 15 Mar 2012 22:34:55 +0000 (UTC) Date: Thu, 15 Mar 2012 23:34:55 +0100 From: Jeremie Le Hen To: Bryan Drewery Message-ID: <20120315223454.GA30360@felucia.tataz.chchile.org> Mail-Followup-To: Bryan Drewery , freebsd-hackers@freebsd.org References: <4F4AFB53.8020503@shatow.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F4AFB53.8020503@shatow.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org, jeremie@le-hen.org Subject: Re: compiling ports with SSP (was: [PATCH] Add -lssp_nonshared to GCC's LIB_SPEC unconditionally)= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 22:35:05 -0000 Hi Bryan On Sun, Feb 26, 2012 at 09:41:07PM -0600, Bryan Drewery wrote: > > Thanks for this patch [1]! > > I've been building my ports tree with -fstack-protector on FreeBSD 6, 7 > and 8. Once I upgraded to 8, I started running into the issue [2] this > patch is fixing. > > I have a situation where non-ports applications are compiling > statically, which ran into this. Specifically, the application is > linking in security/openssl statically, which of course was compiled > with -fstack-protector. Adding the /usr/lib/libc.ld fixed it without > needing to hack at the failing non-port application. > > Would be nice if this, and PR 138228 were finally committed. > > Bryan Drewery > > [1] http://lists.freebsd.org/pipermail/freebsd-hackers/2011-June/035538.html > [2] http://gcc.gnu.org/ml/gcc-help/2006-05/msg00092.html Wow, the perspective provided by those two posts makes me dizzy. This has been a very long standing project. The base system is now compiled with SSP, but doing so for ports still requires some manual hacking unfortenately. I've proposed a patch to compile ports with SSP a few years ago, but some ports with special building strategy suffered the problem described in [2]. Then I learned the possibilities of ld scripts and provided the patch in [1] last year. I think we have all the bits necessary to be able to compile ports with SSP painlessly. First the patch in [1] has to be committed in the base system. I think this can be done in CURRENT without any problem, I run it myself on my own servers without problem. Unfortunately it will probably never appear in RELENG_9 because it may be deemed too dangerous to make such a change in a stable branch. It would be nice to hear what kib@ and kan@ think about this. Next, the patch to bsd.port.mk in this PR [3] has to be applied to be able to compile ports with SSP using a single knob. (Other patches along this one can be thrown away, they were required hacks back when the libc ld script didn't exist.) Then portmgr@ will naturally want to make a full port build with this knob turned on to check, but last time I was told they had very few resource and that this couldn't be scheduled in the next couple of week, IIRC. I admit the situation is partly my fault, because I did the fun technical work but I didn't keep up with the "lobbying" part :). I asked once or twice, without success, and then went to other subjects. I would be really glad if we could proceed with this. FreeBSD-9.0 has just been release, this is probably a good time to step forward. [3] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/138228 Cheers, -- Jeremie Le Hen Men are born free and equal. Later on, they're on their own. Jean Yanne From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 16 05:49:06 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB95D1065673; Fri, 16 Mar 2012 05:49:06 +0000 (UTC) (envelope-from maninya@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4DF908FC14; Fri, 16 Mar 2012 05:49:05 +0000 (UTC) Received: by yhgm50 with SMTP id m50so4688548yhg.13 for ; Thu, 15 Mar 2012 22:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=16G+WqxRtP1LHUbTz8tjvldmLBes43tpm/8CiPhNBVE=; b=uRYmCGJJ/HOq4XoraTE8Vek1RnALBYNyDGGwfL6DFIOT8W+mFVU0BWwf31D5hl+Dr/ oYWbzeCgsFHHB5Q8dmIGIs9s6t3TN0ducYQ0UNXjIqK78w16WaGgWgo4cRwCHzM97GJf Ad5NXMPIq+S6IDOxhsnxwBmBlc1XkljcnFAm0gBMZssc7NY0DQI26pkTFM7coPI7IaQ/ jWTvov4FSN5ielFJOQCRV8CAynzAlgsu7fx2tp0ClrE+bFsMiC92HxKCeF/5Mem9fyiU hALnElhxT6/l1y68zHID4aT1u8Og4Gexh++8iz1WSa0/M4f9f8HlD1rI1mn1DnS7rg+8 tpEw== MIME-Version: 1.0 Received: by 10.236.124.3 with SMTP id w3mr1317996yhh.101.1331876945659; Thu, 15 Mar 2012 22:49:05 -0700 (PDT) Received: by 10.147.24.14 with HTTP; Thu, 15 Mar 2012 22:49:05 -0700 (PDT) In-Reply-To: <4F60FF28.8010104@freebsd.org> References: <4F60FF28.8010104@freebsd.org> Date: Fri, 16 Mar 2012 11:19:05 +0530 Message-ID: From: Maninya M To: Julian Elischer , Artem Belevich Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Capture states of all processes at the same time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 05:49:06 -0000 I am unable to enter DDB. I used the command from this link: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html where it says: ------ The second scenario is to drop to the debugger once the system has booted. There are two simple ways to accomplish this. If you would like to break to the debugger from the command prompt, simply type the command: # sysctl debug.kdb.enter=1 ------ But when I type that the computer hangs! What do I do? My primary aim is to get the process states of all processes running at a particular time, save them and be able to retrieve them when needed so I can run the processes from those states. Also how can I know in which CPU (I am using an intel i5 multicore system) core each process is running? On 15 March 2012 01:57, Julian Elischer wrote: > On 3/14/12 12:02 PM, Artem Belevich wrote: > >> On Wed, Mar 14, 2012 at 11:25 AM, Maninya M wrote: >> >>> Then typed this to force a panic: >>> >>> sysctl debug.kdb.panic=1 >>> >>> The computer just hung after this, and after waiting for a while I >>> pressed >>> the reboot button. >>> It said "no core dumps found" while rebooting. >>> >> First, make sure you have swap space configured. If minidump is not >> enabled (check sysctl debug.minidump) you will need to make sure you >> have more swap space than physical memory. >> Then make sure that dump device is set up correctly. See dumpdev in >> rc.conf(5) >> >> If that didn't work, you may be running into the issue in PR kern/155421: >> http://www.freebsd.org/cgi/**query-pr.cgi?pr=kern%2F155421&**cat= >> >> Alas, I don't know what to do about that. >> > > or just do "ps" from ddb and then continue. > > you can set things up in 9 (and maybe 8, I don't know) to capture the ddb > output.. > > > --Artem >> ______________________________**_________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/**mailman/listinfo/freebsd-**hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@** >> freebsd.org " >> >> > -- Maninya From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 16 06:08:07 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5564D106566B; Fri, 16 Mar 2012 06:08:07 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id EE4B08FC16; Fri, 16 Mar 2012 06:08:06 +0000 (UTC) Received: by ghrr20 with SMTP id r20so4672306ghr.13 for ; Thu, 15 Mar 2012 23:08:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=MtQtUPvivaLDY1zGRCymY3RaH83LrcMC+ooMdgyA/ig=; b=kiApndL7OrZ7ZcNqGmcavWKgDn1AYbUNKeRXfrk+b30HhCrYQm8lTSpi1kpkvQFF/A 7yWMPkb/r/sG0Jk5f1nvoVlMQkVWh/v0jL3SUIvueqA5zmomBolg0yjkeE14rQM4fH1W fRKRP9MGeHHg3qduoilqxZDwes/whMLJVhvy2LptYJ0ZSOW+B+WFPcy0DYDUBZhMzGUF dYgnyuYPGh8GvRH89u0N+lmm981si1AImbcDBGDwW3jJaIVhQWC8ewBNQpk09x6Se4ck OGACyqqlwc3s4YxMcPptAMi5rBk3ofnAh+HyP/d4ewsJZ9tC7cEr4hWtLTD6YFt1Ynar T7rA== MIME-Version: 1.0 Received: by 10.236.170.134 with SMTP id p6mr1387104yhl.81.1331878086264; Thu, 15 Mar 2012 23:08:06 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.147.181.4 with HTTP; Thu, 15 Mar 2012 23:08:06 -0700 (PDT) In-Reply-To: References: <4F60FF28.8010104@freebsd.org> Date: Thu, 15 Mar 2012 23:08:06 -0700 X-Google-Sender-Auth: d8eSkT4a3Ojr8KzYqN010Y_sZy8 Message-ID: From: Artem Belevich To: Maninya M Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Capture states of all processes at the same time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 06:08:07 -0000 On Thu, Mar 15, 2012 at 10:49 PM, Maninya M wrote: > # sysctl debug.kdb.enter=1 > > ------ > > But when I type that the computer hangs! Did you by any chance do that from a terminal window in X11 environment? If that's the case, then kernel debugger is running, you just don't see anything because it can print stuff out only on console or serial port. If that indeed what happened, typing c and then ENTER should unhang your system. After that you can switch to the console with CTRL-ALT-F1 and enter debugger from there. --Artem From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 16 07:09:23 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7648106564A for ; Fri, 16 Mar 2012 07:09:23 +0000 (UTC) (envelope-from kotasaikrishna28@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 07BD48FC0A for ; Fri, 16 Mar 2012 07:09:22 +0000 (UTC) Received: by wern13 with SMTP id n13so4724418wer.13 for ; Fri, 16 Mar 2012 00:09:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=sYre16eNaJomB9bwJ21kz4bJlVvfUTvUotG5RFFBcgA=; b=drUH74K20xezsTao8RR5EQ0O7SjhWOahcwQHj6vWDPwBA7ICjY4jY0JH90ZzysqB/r ve7waTkJj5HxJFrriDukztxMxjZAJdGXEe7DHAunzMeyuxhWFD+mSMWpKoiqeNpiU+yE VN4Rs65fppKZvVrnNcqRRZJnb5H8AzC09QZiaQFj8PiiakQ9yVRN8FjPPPpYcWPk0eKZ prmaHZwz4g3BTcGrwfIuDM15bNzx4pAoNjdxyNiEU/U/WmDUN1qaOaAL5GSoC2uT1Nfh oLvWNoEEuxV0g2jLZJEgpr4ZSGwczDFDEHHFS4Tu+qkeITgq/s2PLiPuQQ9PjjyH7AEK WlAg== MIME-Version: 1.0 Received: by 10.180.100.2 with SMTP id eu2mr3901984wib.1.1331881756262; Fri, 16 Mar 2012 00:09:16 -0700 (PDT) Received: by 10.223.114.73 with HTTP; Fri, 16 Mar 2012 00:09:16 -0700 (PDT) Date: Fri, 16 Mar 2012 12:39:16 +0530 Message-ID: From: kota saikrishna To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: How to use pfind in freeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 07:09:24 -0000 I need to get process data structure using a pid. I found the pfind function which returns struct proc * but when i tried to use pfind function it is showing ---undefined reference to `pfind' Can any one suggest how to use pfind() function? From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 16 09:08:31 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9060E106566C for ; Fri, 16 Mar 2012 09:08:31 +0000 (UTC) (envelope-from rodrigo@bebik.net) Received: from smtp3-g21.free.fr (smtp3-g21.free.fr [IPv6:2a01:e0c:1:1599::12]) by mx1.freebsd.org (Postfix) with ESMTP id C67E08FC18 for ; Fri, 16 Mar 2012 09:08:28 +0000 (UTC) Received: from oldfaithful.bebik.local (unknown [82.227.164.69]) by smtp3-g21.free.fr (Postfix) with ESMTP id 8DFD1A6227 for ; Fri, 16 Mar 2012 10:08:23 +0100 (CET) Received: by oldfaithful.bebik.local (Postfix, from userid 1001) id 5DF482F188; Fri, 16 Mar 2012 10:13:27 +0100 (CET) Date: Fri, 16 Mar 2012 10:13:27 +0100 From: Rodrigo OSORIO To: freebsd-hackers@freebsd.org Message-ID: <20120316091327.GA27873@oldfaithful.bebik.local> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Subject: Re: How to use pfind in freeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 09:08:31 -0000 On 16/03/12 12:39 +0530, kota saikrishna wrote: > I need to get process data structure using a pid. I found the pfind > function which returns struct proc * but when i tried to use pfind > function it is showing ---undefined reference to `pfind' > Can any one suggest how to use pfind() function? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Hi, pfind and friends looks like kernel only function. I can suggest you to explore the sysctl(3) way to recover the kern.proc structures. There are fexw examples on the internet, you can check a code I wrote few years ago to recover the battery state in my laptop using sysctl ; hope this help. http://www.bebik.net/doku.php/battery_life_and_sysctl_3 Regards, Rodrigo From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 16 11:53:41 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2C349106564A for ; Fri, 16 Mar 2012 11:53:41 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id D8A328FC15 for ; Fri, 16 Mar 2012 11:53:40 +0000 (UTC) Received: from [89.204.130.212] (helo=tiny.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1S8Vit-0007ik-OC; Fri, 16 Mar 2012 12:53:32 +0100 Received: from tiny.Sisis.de (localhost [127.0.0.1]) by tiny.Sisis.de (8.14.5/8.14.3) with ESMTP id q2GBrSSs001738; Fri, 16 Mar 2012 12:53:29 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny.Sisis.de (8.14.5/8.14.3/Submit) id q2GBrSDD001737; Fri, 16 Mar 2012 12:53:28 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Fri, 16 Mar 2012 12:53:27 +0100 From: Matthias Apitz To: Rodrigo OSORIO Message-ID: <20120316115326.GA1727@tiny> References: <20120316091327.GA27873@oldfaithful.bebik.local> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20120316091327.GA27873@oldfaithful.bebik.local> X-Operating-System: FreeBSD 10.0-CURRENT r226986 (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.130.212 Cc: freebsd-hackers@freebsd.org Subject: Re: How to use pfind in freeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 11:53:41 -0000 El día Friday, March 16, 2012 a las 10:13:27AM +0100, Rodrigo OSORIO escribió: > Hi, > > pfind and friends looks like kernel only function. I can suggest you to explore > the sysctl(3) way to recover the kern.proc structures. There are fexw examples > on the internet, you can check a code I wrote few years ago to recover the > battery state in my laptop using sysctl ; hope this help. > http://www.bebik.net/doku.php/battery_life_and_sysctl_3 Hi Rodrigo, Thanks for your pointer to your page; the page has a small typo: % sysctrl hw.acpi.battery it should say "sysctl"; one question: how do you get the output of 'battery' into the status bar (I'musing KDE 3.5.10). Thanks matthias PD: the lines of your mail are filled up to position 191 with trailing blanks; -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 16 12:56:35 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C4C13106564A for ; Fri, 16 Mar 2012 12:56:35 +0000 (UTC) (envelope-from rflynn@acsalaska.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9459E8FC16 for ; Fri, 16 Mar 2012 12:56:35 +0000 (UTC) Received: from [127.0.0.1] (squeeze.lan.rachie.is-a-geek.net [192.168.2.30]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 2F4F37E869; Fri, 16 Mar 2012 04:56:33 -0800 (AKDT) Message-ID: <4F633864.9040305@acsalaska.net> Date: Fri, 16 Mar 2012 13:56:04 +0100 From: Mel Flynn User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: kota saikrishna References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to use pfind in freeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 12:56:35 -0000 On 3/16/2012 08:09, kota saikrishna wrote: > I need to get process data structure using a pid. I found the pfind > function which returns struct proc * but when i tried to use pfind > function it is showing ---undefined reference to `pfind' > Can any one suggest how to use pfind() function? >From userland, see kvm_openfiles(3) and kvm_getprocs(3). -- Mel From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 16 19:55:23 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E689106564A for ; Fri, 16 Mar 2012 19:55:23 +0000 (UTC) (envelope-from ansarm@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 240E18FC12 for ; Fri, 16 Mar 2012 19:55:22 +0000 (UTC) Received: by dald2 with SMTP id d2so6947760dal.13 for ; Fri, 16 Mar 2012 12:55:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=HiwIUNPiimxiYznT75BBUsAA3I5MRPKUc32uN0+rHXE=; b=kClqlQy3ynll4ofL4kAotznvvwGCAkTto9RS2BB/cfVBAX+256tRTKhc0mQszlqVaR O7zMLnzMCNLZReB1xlzXYZexAAY7KovawH0yTil332/uLo7pWj9HqM8pgS0kPzerYhcs XUV8xNDX3qkvaURh8RznGZt5m+0QmhKTBrkRlbNetWZiQHEgtepG1ebj3U82SGWbj+7Y VEF94J6+ELNRiKQGlHBUXu7MndvGHESKcY6XvyzDQa+ZIfVpgCekVuF2IbDRrI9LNksx iw8Hn0vymXD8Dffxypdwt1ZCrluPb5tqCbs3F9IeFTZA2NSd3LJSOX7lH4k6Iz7HShH7 7mdQ== MIME-Version: 1.0 Received: by 10.68.219.200 with SMTP id pq8mr11907255pbc.153.1331927722652; Fri, 16 Mar 2012 12:55:22 -0700 (PDT) Received: by 10.68.201.202 with HTTP; Fri, 16 Mar 2012 12:55:22 -0700 (PDT) Date: Fri, 16 Mar 2012 15:55:22 -0400 Message-ID: From: Ansar Mohammed To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: FreeBSD 9.0 x64 de interface under Hyper-V X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2012 19:55:23 -0000 Hello All, I have two freebsd VMs running in Hyper-V 9.0 x86 and 9.0 x64. On x64 the de0 interface apparenlty does not come up when the system is booted. If I bring the interface down and back upagain (ifconfig de0 down, ifconfig de0 up) it works. On x86 de0 works fine. From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 19:30:17 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 963A710656FC; Sat, 17 Mar 2012 19:30:11 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 42E0A8FC16; Sat, 17 Mar 2012 19:30:09 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so4925805bkc.13 for ; Sat, 17 Mar 2012 12:30:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:sender:date:message-id:user-agent:mime-version :content-type; bh=E7uV0r+60TX/kcP247akN1+fHMWohwhsrd0K00zHIoQ=; b=07iIbFzW9U2Mz4WQ5lSAewWFFgqmDAqi6liBSoWNKmPF0A23t+q8yaG1AZK6W5V24K /dypsUBnxmm1ZepBGnLDZSUsDTN+9rEODZ/C2NsiO+DiOGYK57phW3fMR4h/2PrDa+8o dFZChCvIC+c64/EWmOUJK9+RAkAW/5YOsLRCUStxaNczkM91SY1eesOI5Tr+3WtFNpgZ BDBh6+ulSqU72OvKVVNcsIOUjV64cuXCJOZNySSr+evuvk2du9eemOU7Tuy+i+LfTGcg Nwz7SxEizXo+JQbtjFfGeIPP7DKxp3RtJ3nywjnPnZ1dmlovMX9/ldVaNSM7Lhb3Dn7z BOcw== Received: by 10.204.155.143 with SMTP id s15mr2535306bkw.44.1332012609236; Sat, 17 Mar 2012 12:30:09 -0700 (PDT) Received: from localhost ([95.69.173.122]) by mx.google.com with ESMTPS id u5sm16297722bka.5.2012.03.17.12.30.07 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Mar 2012 12:30:08 -0700 (PDT) From: Mikolaj Golub To: freebsd-hackers@freebsd.org Sender: Mikolaj Golub Date: Sat, 17 Mar 2012 21:30:05 +0200 Message-ID: <8662e3m3eq.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Robert Watson , Kostik Belousov Subject: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 19:30:17 -0000 Hi, Currently we can check and change binary osreldate of another process via procfs(5). Kostik suggested to add a new sysctl for the same purpose and also extend procstat to show osrel. Here are patches I am going to commit if there are no objections or suggestions. http://people.freebsd.org/~trociny/kern_proc_osrel.1.patch http://people.freebsd.org/~trociny/procstat.osrel.1.patch I set the same permissions as for procfs(5) osrel -- so only user can read it, but may be this is too restrictive and p_cansee on read would be ok? I added osrel output to procstat -b option: kopusha:~% procstat -b 2975 PID COMM OSREL PATH 2975 emacs 1000001 /usr/local/bin/emacs-23.3 Would this be ok or someone see a better way? -- Mikolaj Golub From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 19:56:27 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2126106564A for ; Sat, 17 Mar 2012 19:56:27 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.33]) by mx1.freebsd.org (Postfix) with ESMTP id 71DD18FC19 for ; Sat, 17 Mar 2012 19:56:27 +0000 (UTC) Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by dlrexedge02.dlr.de (172.21.163.101) with Microsoft SMTP Server (TLS) id 14.1.355.2; Sat, 17 Mar 2012 20:54:28 +0100 Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub02.intra.dlr.de ([::1]) with mapi id 14.01.0355.002; Sat, 17 Mar 2012 20:54:35 +0100 From: To: , Thread-Topic: FreeBSD 9.0 x64 de interface under Hyper-V Thread-Index: AQHNA67WeBfmUTtOSk6p4Ae2HwG2kJZu59M5 Date: Sat, 17 Mar 2012 19:54:35 +0000 Message-ID: <611243783F62AF48AFB07BC25FA4B1060BEB023F@dlrexmbx02.intra.dlr.de> References: In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.136.11] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: FreeBSD 9.0 x64 de interface under Hyper-V X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 19:56:28 -0000 Hi,=0A= =0A= installed 9.0 x64 yesterday and de0 comes up fine when booting. The only th= ing that does not work is promiscuous mode, but that's a restriction of Hyp= er-V.=0A= =0A= harti=0A= ________________________________________=0A= From: owner-freebsd-hackers@freebsd.org [owner-freebsd-hackers@freebsd.org]= on behalf of Ansar Mohammed [ansarm@gmail.com]=0A= Sent: Friday, March 16, 2012 8:55 PM=0A= To: freebsd-hackers@freebsd.org=0A= Subject: FreeBSD 9.0 x64 de interface under Hyper-V=0A= =0A= Hello All,=0A= I have two freebsd VMs running in Hyper-V=0A= 9.0 x86 and 9.0 x64.=0A= =0A= On x64 the de0 interface apparenlty does not come up when the system=0A= is booted. If I bring the interface down and back upagain (ifconfig=0A= de0 down, ifconfig de0 up) it works.=0A= =0A= On x86 de0 works fine.=0A= _______________________________________________=0A= freebsd-hackers@freebsd.org mailing list=0A= http://lists.freebsd.org/mailman/listinfo/freebsd-hackers=0A= To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"= =0A= =0A= From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 20:37:12 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B7E01065677 for ; Sat, 17 Mar 2012 20:37:12 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 10A718FC17 for ; Sat, 17 Mar 2012 20:37:11 +0000 (UTC) Received: by iahk25 with SMTP id k25so10025497iah.13 for ; Sat, 17 Mar 2012 13:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataix.net; s=rsa; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; bh=hSLY9lYr/bIGTfgJvVaMk9GYqCIk+4BSljYylODcVfk=; b=FOkI5hu2NdaYi04r1Iw3qnHvb6caBjE/DzzXXrFi741UcW3AJxtWBr3qCp172Z7Tt0 oV9WoayJDbaWXHykumtwSLMPvb22ocQe8p/VSk2X6ogHCd0ZIZXFqXjPZi/IS1kuBQIs /I30e4zkbQglB96AVqibRdhoF5X/g5e9hJAyA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-gm-message-state; bh=hSLY9lYr/bIGTfgJvVaMk9GYqCIk+4BSljYylODcVfk=; b=b+eaBYSEiZ7+O4AQINFMmscjOe1REyJG6Tb9A70+LEg9ZqM2FzDXmqAFTmryce5m15 IR+zgz0DRscRp5Qm4250nKd33Oo8m2CtHBcltiHrDXQhqxj3EFNfs3ITTY3ABd3zL+si lYESd0vnQVSwu4R/IYh21ZK4quaipXi0NKTT4/VTd57t0Sp/sneTjkxa5As+SUkUR6y5 0nTHLVwtT2wLRXQZCCSkS9ezKaSUbfGu91E2YzyW69MtAdq4jDVJavpL5Q652Mz/0GvE wzLJnCCqIjUd/m/vWVI9ka/o9v+dk+8EAz9CqrgL8LWDFvkRgdjg5+2Og1xsUqiYGAXe dU+w== Received: by 10.50.156.166 with SMTP id wf6mr2272214igb.31.1332016631273; Sat, 17 Mar 2012 13:37:11 -0700 (PDT) Received: from DataIX.net ([99.112.214.41]) by mx.google.com with ESMTPS id c2sm3614043igj.1.2012.03.17.13.37.09 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Mar 2012 13:37:10 -0700 (PDT) Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.5/8.14.5) with ESMTP id q2HKb866038559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Mar 2012 16:37:08 -0400 (EDT) (envelope-from jhellenthal@DataIX.net) Received: (from jhellenthal@localhost) by DataIX.net (8.14.5/8.14.5/Submit) id q2HKb2SX038344; Sat, 17 Mar 2012 16:37:02 -0400 (EDT) (envelope-from jhellenthal@DataIX.net) Date: Sat, 17 Mar 2012 16:37:02 -0400 From: Jason Hellenthal To: Mikolaj Golub Message-ID: <20120317203702.GA42572@DataIX.net> References: <8662e3m3eq.fsf@kopusha.home.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8662e3m3eq.fsf@kopusha.home.net> X-Gm-Message-State: ALoCoQlu+iIb2w2oR30mZtTzY//zMHXbuYWYGfcPCRAGv23uw0xLoHXMFbnjdGQhGhKj/iHgFtKE Cc: freebsd-hackers@freebsd.org, Robert Watson , Kostik Belousov Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 20:37:12 -0000 On Sat, Mar 17, 2012 at 09:30:05PM +0200, Mikolaj Golub wrote: > Hi, > > Currently we can check and change binary osreldate of another process via > procfs(5). > > Kostik suggested to add a new sysctl for the same purpose and also extend > procstat to show osrel. > > Here are patches I am going to commit if there are no objections or > suggestions. > > http://people.freebsd.org/~trociny/kern_proc_osrel.1.patch > http://people.freebsd.org/~trociny/procstat.osrel.1.patch > > I set the same permissions as for procfs(5) osrel -- so only user can read it, > but may be this is too restrictive and p_cansee on read would be ok? > > I added osrel output to procstat -b option: > > kopusha:~% procstat -b 2975 > PID COMM OSREL PATH > 2975 emacs 1000001 /usr/local/bin/emacs-23.3 > > Would this be ok or someone see a better way? > Would this be a planned MFC to stable/N as well specifcially 8 ? -- ;s =; From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 20:51:29 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 91765106566C; Sat, 17 Mar 2012 20:51:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 68B518FC12; Sat, 17 Mar 2012 20:51:29 +0000 (UTC) Received: from [192.168.2.102] (host86-163-246-207.range86-163.btcentralplus.com [86.163.246.207]) by cyrus.watson.org (Postfix) with ESMTPSA id 3FAAC46B0C; Sat, 17 Mar 2012 16:51:28 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <8662e3m3eq.fsf@kopusha.home.net> Date: Sat, 17 Mar 2012 20:51:25 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <82D45B12-1739-4007-8B23-E8B5565F1BBB@FreeBSD.org> References: <8662e3m3eq.fsf@kopusha.home.net> To: Mikolaj Golub X-Mailer: Apple Mail (2.1257) Cc: freebsd-hackers@freebsd.org, Kostik Belousov Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 20:51:29 -0000 On 17 Mar 2012, at 19:30, Mikolaj Golub wrote: > Currently we can check and change binary osreldate of another process = via > procfs(5). >=20 > Kostik suggested to add a new sysctl for the same purpose and also = extend > procstat to show osrel. >=20 > Here are patches I am going to commit if there are no objections or > suggestions. >=20 > http://people.freebsd.org/~trociny/kern_proc_osrel.1.patch > http://people.freebsd.org/~trociny/procstat.osrel.1.patch >=20 > I set the same permissions as for procfs(5) osrel -- so only user can = read it, > but may be this is too restrictive and p_cansee on read would be ok? >=20 > I added osrel output to procstat -b option: >=20 > kopusha:~% procstat -b 2975 > PID COMM OSREL PATH > 2975 emacs 1000001 /usr/local/bin/emacs-23.3 >=20 > Would this be ok or someone see a better way? Support for writing the field seems to violate the synchronisation = protocol defined for p_osrel in proc.h. In the new world order, is this = simply a documentation bug, or is it also a software bug? Robert= From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 21:00:49 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF611106566B; Sat, 17 Mar 2012 21:00:49 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 061168FC12; Sat, 17 Mar 2012 21:00:48 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q2HL0i6V091486; Sat, 17 Mar 2012 23:00:44 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q2HL0hLC021869; Sat, 17 Mar 2012 23:00:43 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q2HL0hth021868; Sat, 17 Mar 2012 23:00:43 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 17 Mar 2012 23:00:43 +0200 From: Konstantin Belousov To: "Robert N. M. Watson" Message-ID: <20120317210043.GQ75778@deviant.kiev.zoral.com.ua> References: <8662e3m3eq.fsf@kopusha.home.net> <82D45B12-1739-4007-8B23-E8B5565F1BBB@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="26hdtSce1ee+1mvy" Content-Disposition: inline In-Reply-To: <82D45B12-1739-4007-8B23-E8B5565F1BBB@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Mikolaj Golub , freebsd-hackers@freebsd.org Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 21:00:49 -0000 --26hdtSce1ee+1mvy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 17, 2012 at 08:51:25PM +0000, Robert N. M. Watson wrote: >=20 > On 17 Mar 2012, at 19:30, Mikolaj Golub wrote: >=20 > > Currently we can check and change binary osreldate of another process v= ia > > procfs(5). > >=20 > > Kostik suggested to add a new sysctl for the same purpose and also exte= nd > > procstat to show osrel. > >=20 > > Here are patches I am going to commit if there are no objections or > > suggestions. > >=20 > > http://people.freebsd.org/~trociny/kern_proc_osrel.1.patch > > http://people.freebsd.org/~trociny/procstat.osrel.1.patch > >=20 > > I set the same permissions as for procfs(5) osrel -- so only user can r= ead it, > > but may be this is too restrictive and p_cansee on read would be ok? > >=20 > > I added osrel output to procstat -b option: > >=20 > > kopusha:~% procstat -b 2975 > > PID COMM OSREL PATH > > 2975 emacs 1000001 /usr/local/bin/emacs-23.3 > >=20 > > Would this be ok or someone see a better way? >=20 >=20 > Support for writing the field seems to violate the synchronisation protoc= ol defined for p_osrel in proc.h. In the new world order, is this simply a = documentation bug, or is it also a software bug? >=20 This is a documentation bug, I failed to update the field description when added procfs support. --26hdtSce1ee+1mvy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk9k+3oACgkQC3+MBN1Mb4hyOACfZOafnmwN42PCZqU8umJEOPEg 4+cAoMrXPzDbmqfVtQIcGcjak3wkkfZu =k0hP -----END PGP SIGNATURE----- --26hdtSce1ee+1mvy-- From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 21:07:30 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2E13106564A; Sat, 17 Mar 2012 21:07:30 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id C9D628FC08; Sat, 17 Mar 2012 21:07:29 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so4955398bkc.13 for ; Sat, 17 Mar 2012 14:07:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=nrMtZA+2pgZnWnIg+MqV2Yi9xfW8AFnSj2mlos7Zs5c=; b=tzZZCpWoQl3xF6Xyu1didLlR8wDx5Nt8SI8a+0zC1f+RDX7+YjwOteY8aNm41aegd7 LRXoP3Ow6W6MNWR8Hah55lCE3NtlBCSMBHr789f4B+56SZGFjxhoPJpfWFGf7yDzTSmg 2ehoyCL+jXYafi4k/9iRQvIR6/DUlG1h5SJ1NFhpZfNeRTUfWVlcO5igNDcrbfR7EVNu Y8ltp/mGxpvG1tl8AdKlt1K1kIYkU/+cVp2tWLDco5cecI8M5/c5MbVVybC4ZyUMbk8h mTj3U4CHWE4Sgbd/mgvzP6+7Zq9hVOnTkoV82CiyAq5TxZW/9aIrY3U8MbHQje5iE2pH 7khQ== Received: by 10.204.132.80 with SMTP id a16mr2663530bkt.18.1332018448776; Sat, 17 Mar 2012 14:07:28 -0700 (PDT) Received: from localhost ([95.69.173.122]) by mx.google.com with ESMTPS id v2sm16611286bki.7.2012.03.17.14.07.26 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Mar 2012 14:07:27 -0700 (PDT) From: Mikolaj Golub To: Jason Hellenthal References: <8662e3m3eq.fsf@kopusha.home.net> <20120317203702.GA42572@DataIX.net> X-Comment-To: Jason Hellenthal Sender: Mikolaj Golub Date: Sat, 17 Mar 2012 23:07:24 +0200 In-Reply-To: <20120317203702.GA42572@DataIX.net> (Jason Hellenthal's message of "Sat, 17 Mar 2012 16:37:02 -0400") Message-ID: <86haxnrl6b.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-hackers@freebsd.org, Robert Watson , Kostik Belousov Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 21:07:30 -0000 On Sat, 17 Mar 2012 16:37:02 -0400 Jason Hellenthal wrote: JH> Would this be a planned MFC to stable/N as well specifcially 8 ? I plan to MFC to stable/9 if there is no objections. -- Mikolaj Golub From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 21:27:01 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6EF76106566B; Sat, 17 Mar 2012 21:27:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id CE5E18FC12; Sat, 17 Mar 2012 21:27:00 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q2HLQsv7093437; Sat, 17 Mar 2012 23:26:54 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q2HLQrt4021991; Sat, 17 Mar 2012 23:26:53 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q2HLQr4s021990; Sat, 17 Mar 2012 23:26:53 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 17 Mar 2012 23:26:53 +0200 From: Konstantin Belousov To: Mikolaj Golub Message-ID: <20120317212653.GS75778@deviant.kiev.zoral.com.ua> References: <8662e3m3eq.fsf@kopusha.home.net> <20120317203702.GA42572@DataIX.net> <86haxnrl6b.fsf@kopusha.home.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MTTkf4DnJGOOhsxg" Content-Disposition: inline In-Reply-To: <86haxnrl6b.fsf@kopusha.home.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Robert Watson , freebsd-hackers@freebsd.org Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 21:27:01 -0000 --MTTkf4DnJGOOhsxg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 17, 2012 at 11:07:24PM +0200, Mikolaj Golub wrote: >=20 > On Sat, 17 Mar 2012 16:37:02 -0400 Jason Hellenthal wrote: >=20 > JH> Would this be a planned MFC to stable/N as well specifcially 8 ? >=20 > I plan to MFC to stable/9 if there is no objections. I do not see why the merge to stable/8 cannot be done from the technical POV. If Mikolaj has no time or desire to merge to 8, I can help him. --MTTkf4DnJGOOhsxg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk9lAZ0ACgkQC3+MBN1Mb4gpBQCffh4Jl5qEI5tZMrFAzKuN32Pp gYoAn1RbglJT06GX+ln3u3FRcY1kLQyr =k5mL -----END PGP SIGNATURE----- --MTTkf4DnJGOOhsxg-- From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 21:29:03 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A28C1065674; Sat, 17 Mar 2012 21:29:03 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id 82EB88FC18; Sat, 17 Mar 2012 21:29:02 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id BC17B359911; Sat, 17 Mar 2012 22:29:01 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id A174528470; Sat, 17 Mar 2012 22:29:01 +0100 (CET) Date: Sat, 17 Mar 2012 22:29:01 +0100 From: Jilles Tjoelker To: Mikolaj Golub Message-ID: <20120317212901.GA44534@stack.nl> References: <8662e3m3eq.fsf@kopusha.home.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8662e3m3eq.fsf@kopusha.home.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Kostik Belousov , freebsd-hackers@freebsd.org, Robert Watson Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 21:29:03 -0000 On Sat, Mar 17, 2012 at 09:30:05PM +0200, Mikolaj Golub wrote: > I added osrel output to procstat -b option: > kopusha:~% procstat -b 2975 > PID COMM OSREL PATH > 2975 emacs 1000001 /usr/local/bin/emacs-23.3 > Would this be ok or someone see a better way? Hmm, this means that procstat is not supposed to be used from scripts as it is apparently OK to change its output format like this? In some ways, querying via ps would be better for scripts since it allows things like ps -p PID -o KEYWORD= which do not need additional parsing except that many of the newer things in procstat do not have ps keywords. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 21:38:28 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A80D106566B; Sat, 17 Mar 2012 21:38:28 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 536BE8FC0A; Sat, 17 Mar 2012 21:38:26 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so4963966bkc.13 for ; Sat, 17 Mar 2012 14:38:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=iJSkbWYLUT+lX3qFv0s2D0u4995/fP3r23Qdf6+F3CE=; b=G3C8IBEp+fmzPNAiAKi9sslL9wQCMTOsQqIG7c+IT4RFzB89G8AJeusUUZwBSOb1Hj fp4BneFjyAvbLf/ET9O2z0hZuu56QObm+qpJSAw7vkR8/8/nzOtbNzI2KoMHcLuBEZn8 ZDxWt1uV6NsAUUyy0qf9fepix02O79owi7PwmT/k9mKA4Z7f5gyDE4VdtslvQEQOH6KR 9AmKDKl8IROV2SIIETkfBTdZkYYxmdaGrMOqLeZ8Zm8hOBb1787rG0zyYjeh/gSB8xZ4 7uIInZlhKqJ3WESEIO2R/PrhIdk9IYgVBNdQ71zI/FUI1IoxaGmy0Qut4GhBdJjsJFd+ 5w1Q== Received: by 10.204.133.196 with SMTP id g4mr2755872bkt.0.1332020306143; Sat, 17 Mar 2012 14:38:26 -0700 (PDT) Received: from localhost ([95.69.173.122]) by mx.google.com with ESMTPS id f6sm16699199bkg.10.2012.03.17.14.38.23 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Mar 2012 14:38:24 -0700 (PDT) From: Mikolaj Golub To: Konstantin Belousov References: <8662e3m3eq.fsf@kopusha.home.net> <20120317203702.GA42572@DataIX.net> <86haxnrl6b.fsf@kopusha.home.net> <20120317212653.GS75778@deviant.kiev.zoral.com.ua> X-Comment-To: Konstantin Belousov Sender: Mikolaj Golub Date: Sat, 17 Mar 2012 23:38:22 +0200 In-Reply-To: <20120317212653.GS75778@deviant.kiev.zoral.com.ua> (Konstantin Belousov's message of "Sat, 17 Mar 2012 23:26:53 +0200") Message-ID: <86d38asyb5.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Robert Watson , freebsd-hackers@freebsd.org Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 21:38:28 -0000 On Sat, 17 Mar 2012 23:26:53 +0200 Konstantin Belousov wrote: KB> On Sat, Mar 17, 2012 at 11:07:24PM +0200, Mikolaj Golub wrote: >> >> On Sat, 17 Mar 2012 16:37:02 -0400 Jason Hellenthal wrote: >> >> JH> Would this be a planned MFC to stable/N as well specifcially 8 ? >> >> I plan to MFC to stable/9 if there is no objections. KB> I do not see why the merge to stable/8 cannot be done from the technical KB> POV. If Mikolaj has no time or desire to merge to 8, I can help him. If people consider this to be useful, no problem for me to merge to 8. -- Mikolaj Golub From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 17 22:48:54 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 21F80106566C for ; Sat, 17 Mar 2012 22:48:54 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id C7E7C8FC1B for ; Sat, 17 Mar 2012 22:48:53 +0000 (UTC) Received: by iahk25 with SMTP id k25so10191102iah.13 for ; Sat, 17 Mar 2012 15:48:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataix.net; s=rsa; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; bh=52WobT5UeUE9PZ1VL+1fv5rmwp6p+LmZuHLM0RbDpY4=; b=Z80CTxva/qp8bhVJ2FLJt9wHDDOh9bygL1+CPnTfzarbKmue5vMq71J+yBhuvSkhMb TPBNyxzQtJQ9zNG1dTTb6CaDKpg2TwwKYhtXlp0Vjl/jiCvHC6cT9EY0yVgsn2wD4szg a6vEZqJtDcUf0+Ihr5CPfY65xcpi9fgxOiS9E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-gm-message-state; bh=52WobT5UeUE9PZ1VL+1fv5rmwp6p+LmZuHLM0RbDpY4=; b=Q3AbN64czo33F0ipcoGGiFiACQMxV1iWZcgWHiNAWIgjO5Td9N2YUqGVFsJOO3icFE L4VQapNOK2QvOopKjesyHml1NL/Xa8o8WEhHvysEt2VoC7qIpvUJ9yrh5GwtRd6CkSmP 8SmCt5B1X8qd/hcr8sFeq5BsVOU/ZKD3HSC/Q20ZSqUiWk3uPugEQDZfzlp0cT6ZrLFe Oey0/XRH8S9RNwppCydYuIo4qzoVGYGQm3InPyMgbD8mwXHmy6TKo8vWS2LdoTmZDzfW /vo0SVWM8xdPWcT7hQOt1Ri3tlwsQaQS7pwtBcPrtHlQg0lVTME0z+UARUjidvGeGh5+ gANw== Received: by 10.50.182.138 with SMTP id ee10mr2657513igc.43.1332024532966; Sat, 17 Mar 2012 15:48:52 -0700 (PDT) Received: from DataIX.net ([99.112.214.41]) by mx.google.com with ESMTPS id k3sm2698317igq.1.2012.03.17.15.48.51 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Mar 2012 15:48:52 -0700 (PDT) Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.5/8.14.5) with ESMTP id q2HMmmuE059969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Mar 2012 18:48:48 -0400 (EDT) (envelope-from jhellenthal@DataIX.net) Received: (from jhellenthal@localhost) by DataIX.net (8.14.5/8.14.5/Submit) id q2HMmhVi058622; Sat, 17 Mar 2012 18:48:43 -0400 (EDT) (envelope-from jhellenthal@DataIX.net) Date: Sat, 17 Mar 2012 18:48:42 -0400 From: Jason Hellenthal To: Mikolaj Golub Message-ID: <20120317224842.GA43874@DataIX.net> References: <8662e3m3eq.fsf@kopusha.home.net> <20120317203702.GA42572@DataIX.net> <86haxnrl6b.fsf@kopusha.home.net> <20120317212653.GS75778@deviant.kiev.zoral.com.ua> <86d38asyb5.fsf@kopusha.home.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86d38asyb5.fsf@kopusha.home.net> X-Gm-Message-State: ALoCoQnzwbxajMG/ypdUO8HG5TJVzkkqPNb8TW1kvd3m0/liFx84N2PHF+c51sNeMrNmNF3f79wO Cc: Konstantin Belousov , freebsd-hackers@freebsd.org, Robert Watson Subject: Re: a sysctl for process binary osreldate X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 22:48:54 -0000 On Sat, Mar 17, 2012 at 11:38:22PM +0200, Mikolaj Golub wrote: > > On Sat, 17 Mar 2012 23:26:53 +0200 Konstantin Belousov wrote: > > KB> On Sat, Mar 17, 2012 at 11:07:24PM +0200, Mikolaj Golub wrote: > >> > >> On Sat, 17 Mar 2012 16:37:02 -0400 Jason Hellenthal wrote: > >> > >> JH> Would this be a planned MFC to stable/N as well specifcially 8 ? > >> > >> I plan to MFC to stable/9 if there is no objections. > > KB> I do not see why the merge to stable/8 cannot be done from the technical > KB> POV. If Mikolaj has no time or desire to merge to 8, I can help him. > > If people consider this to be useful, no problem for me to merge to 8. > I for one would. It would be nice to see this information on running procs to verify there is not some old running binary that was left behind in an upgrade. -- ;s =;