No Subject
Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one >From foo four >From bar seven To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please test for 8G-OVER-Booting with /boot/loader
Little tip for would-be grub users... I had to play with the compiler flags quite a bit to get a bootable image. I suggest taking the flags used to compile the FreeBSD boot loaders and using them. On Thu, 30 Mar 2000, Vladik wrote: > Hi, for now I am doing this every time (but I also do not > reboot too often). > GRUB has a curses-like based menu thing where you > can specify what to boot and how. You have to > set the config file during the compilation. And then > compile, and then build the floppy with that or install > on to the MBR. And I have not done that yet. > > -- > Vladislav > > Charles Anderson wrote: > > > > Do you do this everytime or just to get things started? > > > > If it's everytime, man that's a pain, if it's just to get things > > started it's easier than what I did. (but now I get a list of what I > > want to boot from the NT bootloader, and I just hit the arrow down to > > FreeBSD and go.) > > > > -Charlie > > On Wed, Mar 29, 2000 at 03:21:39PM -0500, Vladik wrote: > > > Hello, > > > I am not sure if this exactly on topic, > > > but this is how I boot freeBSD partition that is installed > > > beyond cyl 1024 > > > > > > > > > I use GRUB boot loader that understands LBA (www.gnu.org/grub) > > > > > > Once GRUB boots from a floppy, go to GRUB's command prompt and > > > do the following: > > > > > > root (hd0,3,a) # or whatever your FreeBSD root slice is > > > #after the command above, it mounted the partition > > > > > > kernel /kernel -remount > > > boot > > > > > > When kernel boots to the point where it needs to mount a root > > > partion it will ask you, > > > in there you type > > > ufs:/dev/ad0s4a > > > > > > > > > > > > Vladislav > > > > -- > > Charles Anderson[EMAIL PROTECTED] > > > > No quote, no nothin' > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Updating examples /usr/share/examples/ld
| Can someone please update the examples in /usr/share/examples/kld?
|
| It's a bit confusing when it doesn't even compile.
i just submitted a patch to get the kld/cdev module to compile
(and work too ;). i tested this on a -stable box.. but it
should still work for -current.
i used the vn device as an example since i'm still learning
how KLDs work.
see patch below or at:
http://www.barmetta.com/freebsd/examples-kld-cdev.patch
...bryan
--
[EMAIL PROTECTED]
-8<-
diff -rc cdev-old/module/cdevmod.c cdev/module/cdevmod.c
*** cdev-old/module/cdevmod.c Thu Mar 30 21:19:48 2000
--- cdev/module/cdevmod.c Thu Mar 30 21:17:15 2000
***
*** 81,99
/* read */ noread,
/* write */ nowrite,
/* ioctl */ mydev_ioctl,
- /* stop */ nostop,
- /* reset */ noreset,
- /* devtotty */ nodevtotty,
/* poll */ nopoll,
/* mmap */ nommap,
/* strategy */ nostrategy,
/* name */ "cdev",
- /* parms */ noparms,
/* maj */ CDEV_MAJOR,
/* dump */ nodump,
/* psize */ nopsize,
/* flags */ D_TTY,
- /* maxio */ 0,
/* bmaj */ -1
};
--- 81,94
***
*** 109,115
*/
static int
! cdev_load(module_t mod, int cmd, void *arg)
{
int err = 0;
--- 104,110
*/
static int
! cdev_modevent(module_t mod, int cmd, void *arg)
{
int err = 0;
***
*** 117,122
--- 112,119
case MOD_LOAD:
/* Do any initialization that you should do with the kernel */
+ cdevsw_add(&my_devsw);
+ make_dev(&my_devsw, 0, UID_ROOT, GID_OPERATOR, 0644, "%s", "cdev");
/* if we make it to here, print copyright on console*/
printf("\nSample Loaded kld character device driver\n");
***
*** 126,135
break; /* Success*/
case MOD_UNLOAD:
printf("Unloaded kld character device driver\n");
break; /* Success*/
! default: /* we only understand load/unload*/
err = EINVAL;
break;
}
--- 123,136
break; /* Success*/
case MOD_UNLOAD:
+ /* fall through */
+ case MOD_SHUTDOWN:
+ cdevsw_remove(&my_devsw);
+
printf("Unloaded kld character device driver\n");
break; /* Success*/
! default:
err = EINVAL;
break;
}
***
*** 139,142
/* Now declare the module to the system */
! DEV_MODULE(cdev, CDEV_MAJOR, -1, my_devsw, cdev_load, 0);
--- 140,143
/* Now declare the module to the system */
! DEV_MODULE(cdev, cdev_modevent, NULL);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: NFS/Vinum problems
On Friday, 31 March 2000 at 0:23:04 -0500, Systems Administrator wrote: > > panic: lockmgr: pid -2, exclusive lock holder 5 unlocking > > Syncing disks... Timedout SCB handled by another timeout > Timedout handled by another timeout > > That is what I get when doing a 'du -k' on an NFS mount from a remote > machine.. THe machine I am speaking of is the actual nfs server, i'm using > freebsd's default nfsd/mountd flags as specified by rc.conf.. However, > when I do lets say, a du -k on the mounted volume, I get that panic.. If > this is a known bug or if anyone knows how to fix this, get back to me > asap.. Yes, I've seen something like this. My best guess is that there's a problem in the error recovery code in CAM, but that's just a guess. If you want to help, give us more information, at least what I'm asking for in http://www.lemis.com/vinum/how-to-debug.html. In addition, the way you're using NFS would be very helpful. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NFS/Vinum problems
panic: lockmgr: pid -2, exclusive lock holder 5 unlocking Syncing disks... Timedout SCB handled by another timeout Timedout handled by another timeout That is what I get when doing a 'du -k' on an NFS mount from a remote machine.. THe machine I am speaking of is the actual nfs server, i'm using freebsd's default nfsd/mountd flags as specified by rc.conf.. However, when I do lets say, a du -k on the mounted volume, I get that panic.. If this is a known bug or if anyone knows how to fix this, get back to me asap.. Thanks in advance, Jason DiCioccio To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
In message <[EMAIL PROTECTED]> Matthew Dillon writes: : Async should not be used unless you really like restoring crashed : filesystems from tape :-). Oh, and perhaps when one is doing an : initial OS install from CDRom :-). Async itself will not cause a crash, : but if your machine crashes in the middle of a bunch of async writes : you might end up with an unrecoverable filesystem. Sure makes those restores from backup tapes run fast, however :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please test for 8G-OVER-Booting with /boot/loader
Hi, for now I am doing this every time (but I also do not reboot too often). GRUB has a curses-like based menu thing where you can specify what to boot and how. You have to set the config file during the compilation. And then compile, and then build the floppy with that or install on to the MBR. And I have not done that yet. -- Vladislav Charles Anderson wrote: > > Do you do this everytime or just to get things started? > > If it's everytime, man that's a pain, if it's just to get things > started it's easier than what I did. (but now I get a list of what I > want to boot from the NT bootloader, and I just hit the arrow down to > FreeBSD and go.) > > -Charlie > On Wed, Mar 29, 2000 at 03:21:39PM -0500, Vladik wrote: > > Hello, > > I am not sure if this exactly on topic, > > but this is how I boot freeBSD partition that is installed > > beyond cyl 1024 > > > > > > I use GRUB boot loader that understands LBA (www.gnu.org/grub) > > > > Once GRUB boots from a floppy, go to GRUB's command prompt and > > do the following: > > > > root (hd0,3,a) # or whatever your FreeBSD root slice is > > #after the command above, it mounted the partition > > > > kernel /kernel -remount > > boot > > > > When kernel boots to the point where it needs to mount a root > > partion it will ask you, > > in there you type > > ufs:/dev/ad0s4a > > > > > > > > Vladislav > > -- > Charles Anderson[EMAIL PROTECTED] > > No quote, no nothin' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
:>:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: :>[...] :>6 minutes 20 seconds (about 7%). : :I'm seeing the same order of improvement still. : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :[EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK Ok, excellent. I figured out why my I/O rate was still high -- I also hadn't turned on softupdates for /var/tmp, but it didn't make much of a difference since I use -pipe in my compiler options so I am still hanging on around 5-7% too. That's still significant, but not as fun a number as the first one :-). I am coordinating one more patch set with Mike that makes sigprocmask and the core copyout function MP safe (so both copyin and copyout are MP safe). Copyout is basically MP safe already, sigprocmask needed only minor adjustments. Then I'm going to turn the code loose in 5.0 and, in a week or two, backport it to 4.0. Then it will be up to the rest of the community to push the MP lock further, I don't have as much time on my hands as I used to :-). -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
:In message <[EMAIL PROTECTED]> "Matthew D. Fuller" writes: :: The question at task is, is buildworld one of them? I don't think that :: situation comes up a lot in buildworld, but I'm not exactly an authority :: on it... : :About 6 months ago, softupdates made things about 5% faster than async :for makeworld on my PPro 200 + 196M of memory. : :Warner Softupdates is basically going to beat async on just about everything, and beat it *badly* for a bunch of things like /tmp operation. There are a few minor issues with the write-behind code (e.g. that thread on DBM ops and certain contrived random I/O tests being slow), which async is much faster on, but that's just a quirk in the clustering code. I'm working on a patch set which extends the sequential read heuristic to also handle writes. The patch is currently under review and can hopefully be committed to 4.x and 5.x soon (or something like it). Async should not be used unless you really like restoring crashed filesystems from tape :-). Oh, and perhaps when one is doing an initial OS install from CDRom :-). Async itself will not cause a crash, but if your machine crashes in the middle of a bunch of async writes you might end up with an unrecoverable filesystem. Also, async can be awefully hard on the VM system if you are doing a lot of writing - there's a reason why we have write-behind code, even if it has a few bogus cases. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
>:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: >[...] >6 minutes 20 seconds (about 7%). I'm seeing the same order of improvement still. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcvt console driver?
See UPDATING: 2319: The ISA and PCI compatability shims have been connected to the options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old style PCI or ISA drivers (i.e. tx, voxware, etc.) you must include the appropriate option in your kernel config. Drivers using the shims should be updated or they won't ship with 5.0-RELEASE, targeted for 2001. Work is underway to fix pcvt. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
In message <[EMAIL PROTECTED]> "Matthew D. Fuller" writes: : The question at task is, is buildworld one of them? I don't think that : situation comes up a lot in buildworld, but I'm not exactly an authority : on it... About 6 months ago, softupdates made things about 5% faster than async for makeworld on my PPro 200 + 196M of memory. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dual Pathing to SCSI/FC devices.
On Wed, 29 Mar 2000, Brad Knowles wrote: > At 4:28 PM -0800 2000/3/28, Matthew Jacob wrote: > > Yes, we very much has considered this. What's your issue about this, per se? > Myself, I just need to be able to tell the system that SCSI ID x > LUN y is actually the same logical device as SCSI ID v LUN w, but > that one is preferred and the other is backup, and have FreeBSD deal > with doing the re-targeting in the CAM SCSI driver. heh, the buzzword for this is "Dynamic Failover". :) In management circles where the current focus is on 24x7, this is seen as a distinct advantage. > The end result should be that nothing above the CAM SCSI driver > should know that a switch has occurred -- especially not programs > Same deal with fibrechannel as SCSI. > Does that about sum it up? Yes. That was pretty much what I was thinking. "Dual Pathing" the buzzword for using both paths to the device would also be desirable, but then you get into things like wanting to optimise data paths depending on how busy each path is. > Oh, and Carl -- I don't suppose you're looking at Hitachi DF400 > (sometimes rebadged as Comparex D1400) units, are you? If so, I'd No, sorry. I can't actually say what box we're buying yet since we haven't signed the contract. :( Carl. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
So, AGAIN, why was tcpdump moved?
You moved tcpdump into the crypto distribution with revision 1.25 of its Makefile. I am still scratching my head and trying to figure out why, however, since most people expect tcpdump to be in the bin distribution where it's always been. Did you have some really good reason for this which we're just missing here? Thanks! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcvt console driver?
I cvsup'ed and compiled my kernel with the options shown below in my config file. device isa0 device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? # The pcvt console driver (vt220 compatible). device vt0 at isa? options XSERVER # support for running an X server on vt options FAT_CURSOR # start with block cursor # PCVT options documented in pcvt(4). options PCVT_CTRL_ALT_DEL options PCVT_FREEBSD=211 options PCVT_META_ESC options PCVT_NSCREENS=5 options PCVT_PRETTYSCRNS options PCVT_SCREENSAVER I wanted to give a test to pcvt driver, just for fun (and for profit, if it seemed better than syscons). Is pcvt working, at all? Or I should avoid using it? << This is with revision 1.64 of /sys/i386/isa/pcvt/pcvt_drv.c >> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \ -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \ -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. \ -I../../../include -D_KERNEL -include opt_global.h -elf \ -mpreferred-stack-boundary=2 ../../i386/isa/pcvt/pcvt_drv.c ../../i386/isa/pcvt/pcvt_drv.c:108: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:108: warning: its scope is only this definition or declaration, which is probably not what you want. ../../i386/isa/pcvt/pcvt_drv.c:109: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:111: variable `vtdriver' has initializer but incomplete type ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:119: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:120: conflicting types for `pcprobe' ../../i386/isa/pcvt/pcvt_drv.c:108: previous declaration of `pcprobe' ../../i386/isa/pcvt/pcvt_drv.c: In function `pcprobe': ../../i386/isa/pcvt/pcvt_drv.c:127: dereferencing pointer to incomplete type ../../i386/isa/pcvt/pcvt_drv.c: At top level: ../../i386/isa/pcvt/pcvt_drv.c:142: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:143: conflicting types for `pcattach' ../../i386/isa/pcvt/pcvt_drv.c:109: previous declaration of `pcattach' ../../i386/isa/pcvt/pcvt_drv.c: In function `pcattach': ../../i386/isa/pcvt/pcvt_drv.c:149: dereferencing pointer to incomplete type ../../i386/isa/pcvt/pcvt_drv.c:151: dereferencing pointer to incomplete type ../../i386/isa/pcvt/pcvt_drv.c:214: dereferencing pointer to incomplete type *** Error code 1 - Giorgos Keramidas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Thu, Mar 30, 2000 at 04:00:43PM -0800, a little birdie told me that David O'Brien remarked > On Thu, Mar 30, 2000 at 05:44:53PM -0600, Matthew D. Fuller wrote: > > Does softupdates provide faster performance than async/noatime? > > In general it depends. Softupdates is faster on creating a file and then > deleteing it before both hit the disk. Softupdates nulifies out the > creation. Async would write the file to disk just to turn around and > delete it. > > For somethings mounting `async' is faster. The question at task is, is buildworld one of them? I don't think that situation comes up a lot in buildworld, but I'm not exactly an authority on it... -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Thu, Mar 30, 2000 at 05:44:53PM -0600, Matthew D. Fuller wrote: > Does softupdates provide faster performance than async/noatime? In general it depends. Softupdates is faster on creating a file and then deleteing it before both hit the disk. Softupdates nulifies out the creation. Async would write the file to disk just to turn around and delete it. For somethings mounting `async' is faster. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Wed, Mar 29, 2000 at 10:04:17PM -0800, a little birdie told me that Matthew Dillon remarked > > Ha! I found it. Kirk gets the credit --- softupdates was turned on > in one of the machine's /usr/obj's and off on the other machine's. > > So softupdates improves buildworld times by a significant margin. I've > turned softupdates on on both machines and am rerunning the test. I > expect I will see an improvement closer to what Bob Bishop saw when > he ran the test (7% or so) rather then 20+%. Does softupdates provide faster performance than async/noatime? I keep /usr/src and /usr/obj as such, would it be faster with softupdates? And if so, why? -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
NEVER send test messages to any FreeBSD mailing list but freebsd-test. doing so can result in you being filtered from all the freebsd mailing lists. jmb > From: [EMAIL PROTECTED] (Yellow Dog Communications Inc) > Sender: [EMAIL PROTECTED] > X-Loop: FreeBSD.ORG > Precedence: bulk > > Subject: Mail::Internet test subject > > > This is a test message that was sent by the test suite of > Mail::Internet. > > Testing. > > one > > >From foo > four > > >From bar > seven > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Voxware audio is too fast
I'm still using old voxware driver on 5.0 current system because it is only way to get support for my Pro Audio Spectrum card. But there is one problem on playback. It's 5% too fast and it sounds annoying. If I play these same mp3 files through pcm/sbc driver everything is ok. It's also easy to measure this problem just using time command. pas0 at port 0x388 irq 10 drq 5 on isa0 snd0: pas0: driver is using old-style compatability shims mss_detect, busy still set (0xff) sbc0: at port 0x220-0x22f irq 7 drq 1 on isa0 pcm1: on sbc0 pcm: setmap 1a000, 2000; 0xc5cfa000 -> 1a000 pcm: setmap 1c000, 2000; 0xc5cfc000 -> 1c000 Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My KDE she's broke..
In message <[EMAIL PROTECTED]> Julian Elischer writes: : I did a make world, so THEORETICALLY all teh system libraries should be in : sync .. right? Did you also rebuild kde after doing the make world? If not, you missed one of the entries in UPDATING talking about needing to recompile all C++ applications. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Traceroute
IPSEC is hard-defined into the Makefile...not good, especially for
PicoBSD.
-- snip --
--- /usr/src/usr.sbin/traceroute/Makefile.orig Thu Mar 30 14:16:52 2000
+++ /usr/src/usr.sbin/traceroute/Makefile Thu Mar 30 14:23:28 2000
@@ -5,4 +5,11 @@
BINMODE=4555
+
+.ifndef (NOIPSEC)
CFLAGS+=-DHAVE_SYS_SELECT_H=1 -DHAVE_SETLINEBUF=1 -DHAVE_RAW_OPTIONS=1 \
-DSTDC_HEADERS=1 -DIPSEC
+.else
+CFLAGS+=-DHAVE_SYS_SELECT_H=1 -DHAVE_SETLINEBUF=1 -DHAVE_RAW_OPTIONS=1 \
+ -DSTDC_HEADERS=1
+.endif
+
# RTT Jitter on the internet these days means printing 3 decimal places on
@@ -14,4 +21,7 @@
CLEANFILES+= version.c
+
+.ifndef (NOIPSEC)
DPADD= ${LIBIPSEC}
LDADD= -lipsec
+.endif
-- snip --
--
+-+
| Omachonu Ogali [EMAIL PROTECTED] |
| Intranova Networking Group http://tribune.intranova.net |
| PGP Key ID: 0xBFE60839 |
| PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 |
+-+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No Subject
Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one >From foo four >From bar seven To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My KDE she's broke..
> Sometime recently (in the last month or so a lot of my kde stuff stopped > working. > > they all complain about: > jules# kpanel > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol > "_vt$9exception" > jules# You should be reading -current; this changed before the 4.0 release. You have to rebuild all your C++ binaries. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
My KDE she's broke..
Sometime recently (in the last month or so a lot of my kde stuff stopped working. they all complain about: jules# kpanel /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "_vt$9exception" jules# Not being a library specialist.. does anyone know offhand who's got out of step with who? and what I should do to fix it? I reinstalled the kde-base, and that didn't seem to fix it. I did a make world, so THEORETICALLY all teh system libraries should be in sync .. right? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
> > > >Only the i8254 timecounter hardware currently needs interrupt-disabling, > > > >but it is hopefully never used on SMP machines. > > > > > > Worse. It is used by default on SMP machines which don't sport the > > > PIIX timecounter. > > > > ie. anything using the PIIX3 or older (think 440FX dual P6 systems, etc.) > > On the box below, a relative new dual PIII box, with a Intel > motherboard, does it use the i8254 or the PIIX timecounter ? sysctl kern.timecounter.hardware (should have been hw.timecounter.hardware, but whatever) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Thu, Mar 30, 2000 at 10:05:26AM -0800, Mike Smith wrote: > > >> Just following on from this, one thing that I can see immediately being > > >> very important to me at least is a spinlock in the timecounter structure. > > >> Calcru and various other things call microtime(), and we're going to want > > >> to lock out updates and parallel accesses to the timecounter. What > > >> should we be using for an interrupt-disabling spinlock? > > > > > >Nothing. Accesses to the timecounter struct are already MP safe and fast. > > >Only the i8254 timecounter hardware currently needs interrupt-disabling, > > >but it is hopefully never used on SMP machines. > > > > Worse. It is used by default on SMP machines which don't sport the > > PIIX timecounter. > > ie. anything using the PIIX3 or older (think 440FX dual P6 systems, etc.) On the box below, a relative new dual PIII box, with a Intel motherboard, does it use the i8254 or the PIIX timecounter ? Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Mon Mar 27 17:02:42 CEST 2000 root@:/usr/src/sys/compile/REMIE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (496.66-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387fbff real memory = 268369920 (262080K bytes) config> q avail memory = 257515520 (251480K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02c5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02c509c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 [snip] isab0: at device 18.0 on pci0 isa0: on isab0 pci0: at 18.1 pci0: at 18.2 irq 10 Timecounter "PIIX" frequency 3579545 Hz /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work:Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek@ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
> >> Just following on from this, one thing that I can see immediately being > >> very important to me at least is a spinlock in the timecounter structure. > >> Calcru and various other things call microtime(), and we're going to want > >> to lock out updates and parallel accesses to the timecounter. What > >> should we be using for an interrupt-disabling spinlock? > > > >Nothing. Accesses to the timecounter struct are already MP safe and fast. > >Only the i8254 timecounter hardware currently needs interrupt-disabling, > >but it is hopefully never used on SMP machines. > > Worse. It is used by default on SMP machines which don't sport the > PIIX timecounter. ie. anything using the PIIX3 or older (think 440FX dual P6 systems, etc.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
In message <[EMAIL PROTECTED]> Matthew Dillon writes: : The general problem with the timecounter is that not only is the hardware : indeterminant, but the timecounter structure itself is *NOT* MP safe, : at least not by my read of it. : : It also doesn't appear to be interrupt safe. If a microtime() or : getmicrotime() call is interrupted and the interrupting interrupt calls : microtime(), it can corrupt the data returned by the first guy and : even corrupt the structure. We've hacked the parallel port interrupt to be a fast one on one of our boxes. It is connected to the pps driver which calls getnanotime to timestamp the pps pulse that came in. We've seen, in carefully plotting ntp data, that there are often (1 in a thousand) large dropouts in the times reported. They are in the neighborhood of the clock tick. Since ntp discards the outliers, this was a low priority issue for us given the overall nature of that particular system. At the time I took a look at it, and couldn't see how access to the counter could be mp safe, but didn't have a lot of time to pursue it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Error code 2
KAMIL MUHD wrote: > Hi everyone... > > I got this error evrytime I try to make world no matter how often I > cvsup'ed. I don't know what it is, what is Error code 2 anyway? Is my cc > version is out-of-date? I'm using the GNU gcc-2.95.1. My box is running on > 4.0-CURRENT. Any idea? Is it because I've cvsuped the wrong file? I cvsuped > the 4.x-secure-stable-supfile and 4.x-stable-supfile. > > cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational In /etc/make.conf, you should comment out WANT_CSRG_LIBM. The default math library is in src/lib/msun. Why the csrg math library is still in the src tree is somewhat of a mystery to me. -- Steve - Well, thank you Steve, thak you all. Thanks very much, your suggestion really helps me out. Know I know why... :) __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
:In message <[EMAIL PROTECTED]>, Bruce Ev :ans writes: :>On Wed, 29 Mar 2000, Mike Smith wrote: :> :>> Just following on from this, one thing that I can see immediately being :>> very important to me at least is a spinlock in the timecounter structure. :>> Calcru and various other things call microtime(), and we're going to want :>> to lock out updates and parallel accesses to the timecounter. What :>> should we be using for an interrupt-disabling spinlock? :> :>Nothing. Accesses to the timecounter struct are already MP safe and fast. :>Only the i8254 timecounter hardware currently needs interrupt-disabling, :>but it is hopefully never used on SMP machines. : :Worse. It is used by default on SMP machines which don't sport the :PIIX timecounter. : :-- :Poul-Henning Kamp FreeBSD coreteam member :[EMAIL PROTECTED] "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! The general problem with the timecounter is that not only is the hardware indeterminant, but the timecounter structure itself is *NOT* MP safe, at least not by my read of it. It also doesn't appear to be interrupt safe. If a microtime() or getmicrotime() call is interrupted and the interrupting interrupt calls microtime(), it can corrupt the data returned by the first guy and even corrupt the structure. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
Oops.. some of us are using i8254 on SMP machines. This motherboard is a Intel PR440FX. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #5: Mon Mar 27 20:39:24 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/QUAKE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (198.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 134217728 (131072K bytes) avail memory = 126488576 (123524K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc03c7000. -- Eric Futch New York Connect.Net, Ltd. [EMAIL PROTECTED] Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Thu, 30 Mar 2000, Bruce Evans wrote: > >Nothing. Accesses to the timecounter struct are already MP safe and fast. >Only the i8254 timecounter hardware currently needs interrupt-disabling, >but it is hopefully never used on SMP machines. > >Bruce > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: new pccard.conf scheme, please test!
HI, all. I've just committed new feature for pccardd, but default pccard configuration file is still /etc/pccard.conf.sample because I'd like to see how things go and test them more for about a week. Test version of /etc/defaults/pccard.conf, /etc/pccard.conf are available at http://www.freebsd.org/~iwasaki/pccard/pccard.conf.tar.gz and, patches against the files under src/etc and src/share are available at http://www.freebsd.org/~iwasaki/pccard/pccardd-etc.diff You might need to copy /etc/defaults/pccard.conf to src/etc/defauts/ for make world until src/etc/defauts/pccard.conf is created. Please test them and report your problem to [EMAIL PROTECTED] if anything wrong. Thanks! > iwasaki 2000/03/30 08:01:39 PST > > Modified files: > usr.sbin/pccard/pccardd cardd.h file.c pccard.conf.5 pccardd.8 > pccardd.c > Log: > - default config file changed from /etc/pccard.conf to > /etc/defaults/pccard.conf in pccardd. But system default pccardd > config file is still /etc/pccard.conf.sample specified in /etc/rc.conf > for the testing this changes. > - improved `include' keyword function for error handling. > - now that resource pool (io, irq, mem) can be overridden. > - pccard config entries is searched following the first match rule if > there are more than two entries which have the same card identifier. > > Note that the /etc/defaults/pccard.conf related files is not committed > at this time, will come a week later. I'll prepare the test version > of /etc/defaults/pccard.conf, /etc/pccard.conf and other files soon. > > Reviewed by:imp and nomads in Japan. > > Revision ChangesPath > 1.19 +3 -1 src/usr.sbin/pccard/pccardd/cardd.h > 1.25 +116 -41 src/usr.sbin/pccard/pccardd/file.c > 1.13 +18 -4 src/usr.sbin/pccard/pccardd/pccard.conf.5 > 1.18 +10 -4 src/usr.sbin/pccard/pccardd/pccardd.8 > 1.7 +3 -2 src/usr.sbin/pccard/pccardd/pccardd.c > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: : :> So softupdates improves buildworld times by a significant margin. : : Uh, I think we've known this for a while now. ;-) : : Still, I'm looking forward to finding out what the new timings :are for SMP builds with the new code (both with and without :softupdates), and I still can't wait to get this stuff MFC's to :4.0-STABLE. : :== :Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV 4694.193u 1477.722s 1:10:24.37 146.1% 1364+1646k 10077+4118io 1734pf+0w 5.0 softupdates on 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w 5.0 softupdates on 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w 4.0 softupdates off 4745.062u 1668.094s 1:28:58.04 120.1% 1323+1601k 8022+251525io 1787pf+0w 4.0 softupdates off 4712.080u 1678.329s 1:16:29.38 139.2% 1330+1609k 11714+130429io 1692pf+0w 4.0 softupdates on 4708.749u 1674.349s 1:16:20.60 139.3% 1331+1608k 11512+130477io 1479pf+0w 4.0 softupdates on 6 minutes 20 seconds (about 7%). I am still getting a major difference in the I/O stats, though it is much less then before. But now I have no clue as to why that last I/O parameter is so different. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please test for 8G-OVER-Booting with /boot/loader
Do you do this everytime or just to get things started? If it's everytime, man that's a pain, if it's just to get things started it's easier than what I did. (but now I get a list of what I want to boot from the NT bootloader, and I just hit the arrow down to FreeBSD and go.) -Charlie On Wed, Mar 29, 2000 at 03:21:39PM -0500, Vladik wrote: > Hello, > I am not sure if this exactly on topic, > but this is how I boot freeBSD partition that is installed > beyond cyl 1024 > > > I use GRUB boot loader that understands LBA (www.gnu.org/grub) > > Once GRUB boots from a floppy, go to GRUB's command prompt and > do the following: > > root (hd0,3,a) # or whatever your FreeBSD root slice is > #after the command above, it mounted the partition > > kernel /kernel -remount > boot > > When kernel boots to the point where it needs to mount a root > partion it will ask you, > in there you type > ufs:/dev/ad0s4a > > > > Vladislav -- Charles Anderson[EMAIL PROTECTED] No quote, no nothin' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent changes made to pcm
Well, it looks as if some changes were made to pcm. Specifically, it looks as if changes were made to address the problem of RealPlayer not stopping the clip immediately after pressing stop. Before the changes, RealPlayer (all versions) would keep playing the clip ~ 3 secs after pressing stop. Now, it stops playing the clip almost immediately after pressing stop. In the wake of these changes, now RealPlayer's sound gets interrupted very easily after opening/closing windows. Also, the previous pcm changes performed much better under high CPU loads. Now, pcm chokes under CPU loads. I may be wrong, but it looks to me like there's a tradeoff here: if you fix pcm so that RealPlayer stops playing the clip sooner after pressing stop, it performs noticeable worse under moderate to heavy cpu loads. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Performance drop in sound (pcm driver or scheduler?)
I just rebuilt by kernel this morning at around 2:00 AM from a fresh cvsup. Now, the sound driver doesn't perform as well as it used to. For example, playing audio clips in realplayer sometimes skips or cuts out when I open up windows, etc. My Mar 28 build of the kernel doesn't have this behavior. I have the ESS 1868 ISA sound card. Maybe it was a change in the scheduler that did it? At any rate, I'm noticing a drop in performance when I play mp3's or even low-quality audio clips with RealPlayer. I'm thinking that if the sound driver isn't at fault, then it's gotta be changes in the scheduler that's causing the sound apps to not get the CPU time it used to. Again, I'm comparing kernels that were built Mar 28 and Mar 30, the Mar 30 build having the noticable drop in sound driver quality. Basically, I don't really notice any difference overall in system performance between the two, but the pcm driver doesn't seem to be performing as good as it did as of mar 28 and before. I'm guessing that it's the pcm driver's fault, but I just want to cover all bases since someone did mention the new sched. code. What pieces of both were changed between Mar 28 and Mar 30? - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What is the status of the mmap support in the pcm driver?
[Charset koi8-r unsupported, filtering to ASCII...] > Hi, > > Does anybody can clarify what is current status of the mmap support in the pcm > driver? I'm trying to get sound in the quakeforge working, but only managed to > get famous "dsp_mmap." message in kernel logs instead of sound :(. not present in 3.x, don't know about 4.x/5.x cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel building problems/room-for-improvement
Adrian Chadd <[EMAIL PROTECTED]> writes: > I agree that vnode_if.h needs to be in the sys/ tree for this, but I > don't think it needs to be checked into CVS. It means any time > someone modifies vnode_if.src a whole new vnode_if.h could possibly > be generated, causing unnecessary repobloat. Right, but that's the same as with syscall.h et al. > How about having it built as part of populating /usr/include/sys/ ? That would also work. The reason why I didn't do it that way was because there didn't seem to be any simple way of adding that generation of vnode_if.h into src/include/Makefile. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
What is the status of the mmap support in the pcm driver?
Hi, Does anybody can clarify what is current status of the mmap support in the pcm driver? I'm trying to get sound in the quakeforge working, but only managed to get famous "dsp_mmap." message in kernel logs instead of sound :(. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
In message <[EMAIL PROTECTED]>, Bruce Ev ans writes: >On Wed, 29 Mar 2000, Mike Smith wrote: > >> Just following on from this, one thing that I can see immediately being >> very important to me at least is a spinlock in the timecounter structure. >> Calcru and various other things call microtime(), and we're going to want >> to lock out updates and parallel accesses to the timecounter. What >> should we be using for an interrupt-disabling spinlock? > >Nothing. Accesses to the timecounter struct are already MP safe and fast. >Only the i8254 timecounter hardware currently needs interrupt-disabling, >but it is hopefully never used on SMP machines. Worse. It is used by default on SMP machines which don't sport the PIIX timecounter. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel building problems/room-for-improvement
On Thu, Mar 30, 2000, Assar Westerlund wrote: > I would appreciate some feedback (in the form of commits also works) > on two small issues (I've also opened PR's on these). > > 1. Due to vnode_if.h not getting installed, you need to have kernel >source (namely vnode_if.src and vnode_if.pl) to build any file >system to be loaded as a kernel module. This is unfortunate and >should be fairly easy to solve by installing vnode_if.h. See PR >kern/17613. > I agree that vnode_if.h needs to be in the sys/ tree for this, but I don't think it needs to be checked into CVS. It means any time someone modifies vnode_if.src a whole new vnode_if.h could possibly be generated, causing unnecessary repobloat. How about having it built as part of populating /usr/include/sys/ ? Adrian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
On Wed, 29 Mar 2000, Mike Smith wrote: > Just following on from this, one thing that I can see immediately being > very important to me at least is a spinlock in the timecounter structure. > Calcru and various other things call microtime(), and we're going to want > to lock out updates and parallel accesses to the timecounter. What > should we be using for an interrupt-disabling spinlock? Nothing. Accesses to the timecounter struct are already MP safe and fast. Only the i8254 timecounter hardware currently needs interrupt-disabling, but it is hopefully never used on SMP machines. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel building problems/room-for-improvement
I would appreciate some feedback (in the form of commits also works) on two small issues (I've also opened PR's on these). 1. Due to vnode_if.h not getting installed, you need to have kernel source (namely vnode_if.src and vnode_if.pl) to build any file system to be loaded as a kernel module. This is unfortunate and should be fairly easy to solve by installing vnode_if.h. See PR kern/17613. 2. It's hard to build some KLD that use macros from without optimization in some cases. The particular case that I triggered was the definition of __cursig in as `extern __inline' instead of `static __inline'. I don't think there's any particular good reason to not have everything build without -O and the fix (included in the PR) for this problem is trivial. See PR kern/17614. Comments? /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Using packed structs to gain cheap SMP primatives
Alfred Perlstein <[EMAIL PROTECTED]> writes: > I'm aware of this, the problem is that tz may move in either > direction. Why not just ignore the timezone argument? That hasn't been relevant for a long time. The timezone information is kept in user-space. >From gettimeofday(2): Note: timezone is no longer used; this information is kept outside the kernel. And single unix standard says: If tzp is not a null pointer, the behaviour is unspecified. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: > So softupdates improves buildworld times by a significant margin. Uh, I think we've known this for a while now. ;-) Still, I'm looking forward to finding out what the new timings are for SMP builds with the new code (both with and without softupdates), and I still can't wait to get this stuff MFC's to 4.0-STABLE. -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
At 9:45 PM -0500 2000/3/29, Chuck Robey wrote: >> Difference: 19 minutes, or a 21% improvement. Bob Bishop got 7% with an >> earlier patch (hopefully his system is no longer locking up and he can >> repeat his test with the current stuff). > > Goddamn. That's significant! Congratulations, Matt. Did it again! You're not kidding! This is OUTSTANDING! I can't wait for this stuff to get MFC'ed to 4.0-STABLE -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kern/8324
On Mar 20, 11:00am, Archie Cobbs wrote:
} Subject: Re: kern/8324
} Don Lewis writes:
} > This patch (vs the 3.4-STABLE version of tty.c) causes SIGIO to be
} > sent when a regular or pseudo tty becomes writeable.
} >
} >
} > --- tty.c.orig Sun Aug 29 09:26:09 1999
} > +++ tty.c Sat Mar 18 03:09:32 2000
} > @@ -2133,6 +2133,8 @@
} >
} > if (tp->t_wsel.si_pid != 0 && tp->t_outq.c_cc <= tp->t_olowat)
} > selwakeup(&tp->t_wsel);
} > + if (ISSET(tp->t_state, TS_ASYNC) && tp->t_sigio != NULL)
} > + pgsigio(tp->t_sigio, SIGIO, (tp->t_session != NULL));
} > if (ISSET(tp->t_state, TS_BUSY | TS_SO_OCOMPLETE) ==
} > TS_SO_OCOMPLETE && tp->t_outq.c_cc == 0) {
} > CLR(tp->t_state, TS_SO_OCOMPLETE);
} >
} >
} > BTW, I had to add:
} > fcntl(1, F_SETOWN, getpid());
} > to the test program since there is no longer a default target to send
} > the signal to. The old scheme had the defect of sending SIGIO to the
} > process group that owned the terminal, which implied that the terminal
} > had to be the controlling terminal for the process group. This limited
} > a process to only receiving SIGIO from one terminal device even if it
} > had more than one open and it wanted to receive SIGIO from all of them.
} > Also, SIGIO was sent to the entire process group, but it may be desireable
} > to limit this to one process. I wonder if it might make sense to go
} > back to the old default for tty devices so that processes only receive
} > SIGIO when they are in the foreground ...
}
} Don-
}
} After applying your patch to kern/tty.c and adding the F_SETOWN,
} the problem indeed seems to go away..
}
} Is this patch ready to be committed, or do we need more reviewers?
Sorry for the delay, I was out of town most of last week and sick most
of this week.
It's probably safe to commit to -current if someone can give it a quick
test there. Unfortunately I don't have a box running -current to test
it on.
Now, on to some more of my 6280 unread email messages :-(
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
BUILD FIXED (was: build broken for libobjc on RELENG_4)
build breakage due to libobjc has been fixed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
