Re: pgbench performance is lagging compared to Linux and DragonflyBSD?
Hello, Erik. You wrote 7 ноября 2012 г., 19:11:03: EC> That thread starts here: EC> http://lists.freebsd.org/pipermail/freebsd-arch/2010-April/010143.html Year 2010! And we still limited by MAXPHYS (128K) transfers :( -- // Black Lion AKA Lev Serebryakov ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] reducing arp locking
On 08.11.2012 14:24, Andre Oppermann wrote: On 08.11.2012 00:24, Alexander V. Chernikov wrote: Hello list! Currently we need to acquire 2 read locks to perform simple 6-byte copying from arp record to packet ethernet header. It seems that acquiring lle lock for fast path (main traffic flow) is not necessary even with current code. My tests shows ~10% improvement with this patch applied. If nobody objects I plan to commit this change at the end of next week. This is risky and prone to race conditions. The copy of the MAC address should be done while the table read lock is held to protect against the It is done exactly as you say: table read lock is held. entry going away. You can either return with table lock held and drop it after the copy, or you could a modified lookup function that takes a pointer for the copy destination, do the copy with the read lock, and then return. If no entry is found an error is returned and obviously no copy is done. -- WBR, Alexander ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] reducing arp locking
On 08.11.2012 11:25, Alexander V. Chernikov wrote: On 08.11.2012 14:24, Andre Oppermann wrote: On 08.11.2012 00:24, Alexander V. Chernikov wrote: Hello list! Currently we need to acquire 2 read locks to perform simple 6-byte copying from arp record to packet ethernet header. It seems that acquiring lle lock for fast path (main traffic flow) is not necessary even with current code. My tests shows ~10% improvement with this patch applied. If nobody objects I plan to commit this change at the end of next week. This is risky and prone to race conditions. The copy of the MAC address should be done while the table read lock is held to protect against the It is done exactly as you say: table read lock is held. Right. Sorry. I didn't immediately get that the IF_AFDATA_LOCK is the table lock. -- Andre entry going away. You can either return with table lock held and drop it after the copy, or you could a modified lookup function that takes a pointer for the copy destination, do the copy with the read lock, and then return. If no entry is found an error is returned and obviously no copy is done. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: pgbench performance is lagging compared to Linux and DragonflyBSD?
EC> That thread starts here: EC> http://lists.freebsd.org/pipermail/freebsd-arch/2010-April/010143.html Year 2010! And we still limited by MAXPHYS (128K) transfers :( put options MAXPHYS=2097152 in your kernel config. EVERYTHING works in all production machines for over a year the only exception is my laptop with OCZ petrol SSD that hangs on any transfer >1MB, i've set it to 0.5MB here. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] reducing arp locking
On 08.11.2012 00:24, Alexander V. Chernikov wrote: Hello list! Currently we need to acquire 2 read locks to perform simple 6-byte copying from arp record to packet ethernet header. It seems that acquiring lle lock for fast path (main traffic flow) is not necessary even with current code. My tests shows ~10% improvement with this patch applied. If nobody objects I plan to commit this change at the end of next week. This is risky and prone to race conditions. The copy of the MAC address should be done while the table read lock is held to protect against the entry going away. You can either return with table lock held and drop it after the copy, or you could a modified lookup function that takes a pointer for the copy destination, do the copy with the read lock, and then return. If no entry is found an error is returned and obviously no copy is done. -- Andre ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: pgbench performance is lagging compared to Linux and DragonflyBSD?
On Nov 8, 2012, at 12:56 PM, Wojciech Puchar wrote: >> EC> That thread starts here: >> EC> http://lists.freebsd.org/pipermail/freebsd-arch/2010-April/010143.html >> Year 2010! And we still limited by MAXPHYS (128K) transfers :( > put > options MAXPHYS=2097152 > in your kernel config. > > EVERYTHING works in all production machines for over a year > > > the only exception is my laptop with OCZ petrol SSD that hangs on any > transfer >1MB, i've set it to 0.5MB here. Have you measured the performance increase? I'm also interested in bigger MAXBSIZE as this is what the NFS server uses as maximum transfer size. Linux and Solaris can do up to 1MB. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD on RaspberryPi
Hi, why the console cable is needed ? Sami On Wed, Nov 7, 2012 at 6:01 PM, Tim Kientzle wrote: > WARNING: This is still highly experimental and by no > means ready for "production use", but some folks might > find it interesting. > > To boot FreeBSD on your RaspberryPi, you'll need: > 1) A RaspberryPi. > 2) A serial cable similar to this one: www.adafruit.com/products/954 > 3) An SD card of 2GB or larger > > Download this 111MB file (~1.6G uncompressed): > > http://people.freebsd.org/~kientzle/FreeBSD-RPI-B-r242362-2012-10-30.img.xz > > Uncompress it, dd it onto your SD card, pop it in and apply power. > (The serial cable above can also provide power; just leave the red > lead disconnected until you get the SD card plugged in.) > > > KNOWN BROKEN STUFF > > * There's no framebuffer/syscons yet. Hence the need for a serial cable. > > * The memory is mis-probed (actually a boot loader problem, > not a FreeBSD kernel issue), so you'll only get to use 128MB > (you might be able to change this for a single boot by breaking > into ubldr and editing the FDT by hand) > > * There has been NO attempt to reduce the footprint of this image. > It's a completely stock build of FreeBSD-CURRENT. > (Actually, I have turned off sendmail and a few other things in > rc.conf, > but compensated by building world with full debug enabled.) > > * I've personally not tried USB or Ethernet and have no idea if they > work. > > > HOW TO BUILD YOUR OWN IMAGE > > The script I used to build this image is at: >github.com/kientzle/freebsd-beaglebone > (It was originally developed for BeagleBone.) > > > Enjoy! > > > > Boot message (edited for length): > > > DRAM: 128 MiB > WARNING: Caches not enabled > MMC: bcm2835_sdh: 0 > Using default environment > > In:serial > Out: serial > Err: serial > Net: Net Initialization Skipped > No ethernet found. > Hit any key to stop autoboot: 0 > reading uEnv.txt > > 74 bytes read > Importing environment from mmc ... > reading ubldr > > 728201 bytes read > ## Starting application at 0x0254 ... > Consoles: U-Boot console > Compatible API signature found @7b75220 > Number of U-Boot devices: 1 > > FreeBSD/armv6 U-Boot loader, Revision 1.2 > (root@fci386.localdomain, Wed Nov 7 01:54:47 PST 2012) > DRAM:128MB > > Device: disk > - > /boot/kernel/kernel data=0x300238+0x1ec7c syms=[0x4+0x70f80+0x4+0x56d3c] > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > fdt_start: 0x003DC138 > fdt_reg_valid(): reg#0 (start: 0x0 size: 0x800) valid! > Kernel entry at 0x100100... > Kernel args: (null) > > … > > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.0-CURRENT #3: Wed Nov 7 04:23:11 PST 2012 > root@fci386.localdomain:/usr/obj/arm.armv6/usr/src/sys/RPI-B arm > CPU: Sheeva 88SV581x rev 7 (Marvell core) > Supported features: ARM_ISA THUMB2 JAZELLE ARMv4 Security_Ext > WB enabled LABT branch prediction enabled > 16KB/32B 4-way instruction cache > 16KB/32B 4-way write-back-locking-C data cache > real memory = 134217728 (128 MB) > avail memory = 125685760 (119 MB) > > … > > FreeBSD/arm (raspberry-pi) (ttyu0) > > login: root > FreeBSD 10.0-CURRENT (RPI-B) #3: Wed Nov 7 04:23:11 PST 2012 > > Welcome to FreeBSD! > > … > > root@raspberry-pi:/root # top > > last pid: 490; load averages: 0.63, 0.30, 0.12up 0+00:01:32 > 12:47:50 > 7 processes: 1 running, 6 sleeping > CPU: 0.4% user, 0.0% nice, 0.8% system, 2.3% interrupt, 96.5% idle > Mem: 59M Active, 7312K Inact, 8136K Wired, 10M Buf, 47M Free > Swap: > > PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND > 488 root1 160 10808K 10280K pause0:00 5.27% csh > 490 root1 410 10940K 10080K RUN 0:00 4.84% top > 487 root1 80 10980K 10164K wait 0:00 4.31% login > 484 root1 -80 9848K 9596K piperd 0:00 0.67% logger > 452 root1 420 14724K 2208K select 0:00 0.00% sshd > 486 root1 80 1656K 1396K nanslp 0:00 0.00% sleep > 483 root1 80 10416K 1128K wait 0:00 0.00% sh > > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > -- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: A question about creating a system call
Hi Dave:
This wiki page may be of value:
http://wiki.freebsd.org/AddingAuditEvents
Robert N M Watson
Computer Laboratory
University of Cambridge
On Thu, 8 Nov 2012, dave jones wrote:
Hello,
I know how to create system calls, but I'm a bit confused about
sys/kern/syscalls.master file explained. For example, if I have a
foo system call, following code is added:
532 AUE_NULLSTD { int foo(char *str); }
The question is in column two AUE_NULL, can I replace it with AUE_FOO?
How to determine the system call should be audit or not? Thank you.
Regards,
Dave.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: -lpthread vs -pthread: does -D_REENTRANT matter?
On 8 October 2012 12:17, Eitan Adler wrote: > The only difference between -lpthread and -pthread that I could see is > that the latter also sets -D_REENTRANT. > However, I can't find any uses of _REENTRANT anywhere outside of a few > utilities that seem to define it manually. > > Testing with various manually written pthread programs resulted in > identical binaries, let alone identical results. > > Is there an actual difference between -pthread and -lpthread or is > this just a historical artifact? does anyone know the answer to this question? I've been experimenting but can't find a difference at all. -- Eitan Adler ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] reducing arp locking
On 08.11.2012 03:46, Adrian Chadd wrote: On 7 November 2012 15:24, Alexander V. Chernikov wrote: Hello list! Currently we need to acquire 2 read locks to perform simple 6-byte copying from arp record to packet ethernet header. It seems that acquiring lle lock for fast path (main traffic flow) is not necessary even with current code. My tests shows ~10% improvement with this patch applied. If nobody objects I plan to commit this change at the end of next week. That's a great catch! How'd you discover it? We have lots of FreeBSD routers doing 10G firewalling, so we're very much concerned with forwarding/firewalling performance, constantly looking for something to optimize :) Adrian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Custom FreeBSD usb memstick
hello hackers@ I have a interest in playing around with the scripts that create the memstick image when you run make release... can anyone point me in the right direction, how would I go about modifying the size of the partition that gets created on the memstick image -- Sam Fourman Jr. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Custom FreeBSD usb memstick
If you're just looking for a release on memstick, check out druidbsd http://druidbsd.sourceforge.net/ If you're doing it to learn the process, I'm sure you can learn a few things from druidbsd anyway... Enjoy Dave On 11/08/2012 14:07, Sam Fourman Jr. wrote: > hello hackers@ > > I have a interest in playing around with the scripts that create the > memstick image when you run make release... > can anyone point me in the right direction, how would I go about > modifying the size of the partition that gets created on the memstick > image > -- Dave Robison Sales Solution Architect II FIS Banking Solutions 510/621-2089 (w) 530/518-5194 (c) 510/621-2020 (f) da...@vicor.com david.robi...@fisglobal.com _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] reducing arp locking
On 8 November 2012 13:48, Alexander V. Chernikov wrote: >> That's a great catch! How'd you discover it? > > We have lots of FreeBSD routers doing 10G firewalling, so we're very much > concerned with forwarding/firewalling performance, constantly looking for > something to optimize :) I mean, how'd you go about finding it? Adrian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Custom FreeBSD usb memstick
Slowly working my way to HEAD. 9.0-R is the latest I've done (and still waiting patiently for 9.1-R). Druid is unique in that you can create a custom USB memstick that also can be burned to CD or DVD (with zero modifications). When getting started, keep in mind that you can do these steps on Mac OS X, Linux, Cygwin, and (uh) FreeBSD :) 1. Find/Browse the code here… http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druidbsd/ 2. Get the code… In Tarball form (22.6MB): http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druidbsd/?view=tar or Instructions on how to download with CVS: http://sourceforge.net/projects/druidbsd/develop NOTE: When logging in anonymously, simply press ENTER when prompted for a password NOTE: Use a modulename of druidbsd/druidbsd when checking out the code NOTE: Downloaded module measures about 30MB in size 3. Execute the following: cd druidbsd ./configure NOTE: If you went the CVS route, the first command is instead: cd druidbsd/druidbsd 4. Dependency checks: In the output of "configure" from step 3 above (which is rather small), make sure no commands have been mapped "/bin/false" (except for "false" itself, naturally). Basically, you'll need GNU make, mkisofs, and a few basic shell utilities. 5. [Optional] Customize: If you want to customize the kernel that is used, it's in "mdroot/kernels/" NOTE: If you change the name of the kernel, edit the file "mdroot/boot/menu.rc" (kernel paths are at the top) NOTE: You can load multiple kernels if you want (and configure the menu to display them for selection) If you want to customize the boot menu, that's in "mdroot/boot/menu.rc" If you want to add kernel modules, those go into "mdroot/boot/modules/" If you want to customize the mfsroot, there's a whole framework for that in "dep/freebsd/mfsroot/" (however, you'll need a FreeBSD host to customize that portion). If you want to simply add new commands to DruidBSD, dump new binaries into "src/freebsd/rescue/" NOTE: There's a corresponding "src/freebsd/rescue/lib/" for you to dump library dependencies. If you want to add other miscellaneous files, just dump them into "src/freebsd/". 6. Produce an ISO for mastering to USB stick: make NOTE: Sorry, this has to be GNU make (so on FreeBSD, say "gmake" instead). NOTE: This produces the ISO file (image) of your custom FreeBSD memstick 7. Play Use the instructions here to get your ISO onto physical media: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/tools/ NOTE: Start with "README" NOTE: There are many methods for many operating systems documented and even some tools for download (such as a Win32 GUI tool for imaging the ISO onto USB stick). Remember, that ISO can be burned to optical media _and_ imaged to USB stick (or any hard disk for that matter) without changing anything about the ISO (that's the nature of the DRUID architecture). I demonstrated much of this at the last DevSummit, but it's not part of FreeBSD. If you have any questions, let me know. -- Devin On Nov 8, 2012, at 3:36 PM, Robison, Dave wrote: > Druid is Devin's baby so I will CC him > > I do not think he has done HEAD on druid yet... but it's not a bad idea. > > > Dave > > > On 11/08/2012 15:35, Sam Fourman Jr. wrote: >> On Thu, Nov 8, 2012 at 4:11 PM, Robison, Dave >> wrote: >>> If you're just looking for a release on memstick, check out druidbsd >>> >>> http://druidbsd.sourceforge.net/ >>> >>> If you're doing it to learn the process, I'm sure you can learn a few >>> things from druidbsd anyway... >>> >>> Enjoy >>> >>> Dave >> >> Thank you Dave, >> >> do you build a version of DruidBSD based on HEAD? >> >> im really trying to learn the process, and id like to know how to >> alter the install image size.. then ill start with customization from >> there. >> > > > -- > Dave Robison > Sales Solution Architect II > FIS Banking Solutions > 510/621-2089 (w) > 530/518-5194 (c) > 510/621-2020 (f) > da...@vicor.com > david.robi...@fisglobal.com _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] reducing arp locking
Dear Alexander, If nobody objects I plan to commit this change at the end of next week. LLE_RNLOCK(la); should be LLE_RLOCK(la); in arpresolve Kind regards, Ingo Flaschberger ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Custom FreeBSD usb memstick
On 09/11/2012, at 8:37, Sam Fourman Jr. wrote:
> I have a interest in playing around with the scripts that create the
> memstick image when you run make release...
> can anyone point me in the right direction, how would I go about
> modifying the size of the partition that gets created on the memstick
> image
It uses makefs to create an image that is just the right size for the files
that are included.
I wrote a script that will format a given device and splat the installer stuff
on it, ie
cat >make-usb.sh < ${TMPDIR}/mnt/etc/fstab
sync
umount "${TMPDIR}/mnt"
rm -rf "${TMPDIR}"
EOF
The usage example is specific to my work - I have a big tarball full of
preinstalled ports which the script copies to the USB key along with a script
to install it, but you don't need that, just run..
sh ./make-usb.sh /dev/da1 /usr/obj/usr/src/release/release
(Obviously /dev/da1 should be your USB key, check dmesg etc etc)
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD on RaspberryPi
> On Wed, Nov 7, 2012 at 6:01 PM, Tim Kientzle wrote: > WARNING: This is still highly experimental and by no > means ready for "production use", ... > > To boot FreeBSD on your RaspberryPi, you'll need: > 1) A RaspberryPi. > 2) A serial cable similar to this one: www.adafruit.com/products/954 On Nov 8, 2012, at 9:13 AM, Sami Halabi wrote: > > why the console cable is needed ? > As far as I can tell, the code in FreeBSD-CURRENT does not yet support the video out. So you need a serial console cable to interact with it. You might be able to interact via SSH but that requires a little bit more setup (a root password needs to be set and you need to edit /etc/ssh/sshd_config to allow root logins). If someone knows how to get the video out to work, I'm very interested! Tim ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD on RaspberryPi
It was plain current with plain RPIB kernel config, and for graphic you should uncomment there partition about sysconsole; serial then disabled; Also, if you want ethernet - it's ue device, which also worked, but produced hangs for me in past (Hans IIRC already fixed.this). I'll have some time this weekend, feel free to contact me by gtalk or else, I will play around with my rpi with both serials and vide modes. Regards, Alexander Yerenkow 09.11.2012 6:58 пользователь "Tim Kientzle" написал: > > On Nov 7, 2012, at 8:09 AM, Alexander Yerenkow wrote: > > > Such experiments was tried by me and others in August; I got framebuffer > worked in rca/hdmi; ... > > Where is that code? > > Has anyone merged it to FreeBSD-CURRENT yet? > > Tim > > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
