> Did you have opportunity to play with the soft interrupt
> coalescing we discussed?
Did this message just leak to a mailing list, or would you
be able to expand this (or pass a pointer to mailing lists
where this was discussed) ?
thanks
luigi
> I was able to remove a third of
David O'Brien wrote:
> > > Well, since it didn't, I might as well explain the problem here too.
> > > There are at least two major problems with VIA chips:
> >
> > [data curruption on VIA KT133/133A systems by pushing PCI and memory bus]
> >
> > Are you sure about that?
>
> I am. I was having da
On Tue, 4 Sep 2001, Eugene L. Vorokov wrote:
> > I comitted a fix to -current two months ago. It's still in my -stable
> > tree... if Jordan gives the O.K., I will MFC it to -stable.
> >
> > -Matt
>
> Erm, sorry, but what does MFC mean here ? I
Did you have opportunity to play with the soft interrupt
coalescing we discussed?
I was able to remove a third of the interrupt overhead
from the Tigon III driver, using the approach we discussed
at the user group meeting two months back.
It looks to be a serious win... and it appears to be
appl
> I comitted a fix to -current two months ago. It's still in my -stable
> tree... if Jordan gives the O.K., I will MFC it to -stable.
>
> -Matt
Erm, sorry, but what does MFC mean here ? I see this term used a lot and
I can even guess what it
David O'Brien wrote:
>
> Hi Hackers, et.al.
>
> The PIM Evolution, http://www.ximian.com/products/ximian_evolution/,
> does not run on FreeBSD. The authors have made a change so that it will.
> However, we would like to know if FreeBSD is the odd-man-out, or if the
> authors were lucky Evolutio
It seems David Gilbert wrote:
> I've got a promise ATA-66 controller. According to it's bios screen,
> the hard drives attached to it are UDMA-4 and the two CD-type devices
> are UDMA-2. All four devices are attached with ATA-66 cabling. I
> also have "hw.ata.atapi_dma=1" in loader.conf.
>
> I
Faried Nawaz wrote:
> Next: the OSS plugin builds but doesn't seem to work properly. At
> some point, it tries to set /dev/dsp to stereo, and fails:
>
> tmp = 0;
> if (shm->channels == 2)
> tmp = 1;
> rc = ioctl (audio_fd, SNDCTL_DSP_STEREO, &tmp);
>
"Vladimir A. Jakovenko" wrote:
>
> Hello!
>
> According to UNPv1 SO_REUSEPORT on UDP sockets can be used to bind more than
> one socket to the same port (even with same source ip address). But quick
> look on /sys/netinet/udp_usrreq.c function udp_input() shows that this will
> work as expec
Evan Sarmiento wrote:
>
> Hey,
>
> I have a question about sysent. If a modification
> to a processes p->p_sysent and associated substructures
> are made, are the changes propagated through fork
> to children?
Yes, for fork().
You probably wanted to ask about exec(), though... the answer
for e
Poul-Henning Kamp wrote:
>
> In message <[EMAIL PROTECTED]>, Terry Lambert writes:
> >Zhihui Zhang wrote:
> >>
> >> What is the file system that uses VT_TFS in vnode.h? Is it still available
> >> on FreeBSD? Thanks.
> >
> >Julian added it for TRW Financial Services;
>
> And "TFS" means "Truly e
Terry Lambert wrote:
>
> Zhihui Zhang wrote:
> >
> > What is the file system that uses VT_TFS in vnode.h? Is it still available
> > on FreeBSD? Thanks.
>
> Julian added it for TRW Financial Services; the first public
> reference machine for 386BSD (which later became FreeBSD and
> NetBSD) was r
I've written a script that handles the complete updating of an
existing system from a cvsup through to reboot, and I thought I would
check and see if anybody else was interested enough for me to make
it public (maybe as a port).
I also updated mergemaster to read from a config file so that it can
In message <[EMAIL PROTECTED]>, Terry Lambert writes:
>Zhihui Zhang wrote:
>>
>> What is the file system that uses VT_TFS in vnode.h? Is it still available
>> on FreeBSD? Thanks.
>
>Julian added it for TRW Financial Services;
And "TFS" means "Truly evil File System" :-)
It should be nuked now
Zhihui Zhang wrote:
>
> What is the file system that uses VT_TFS in vnode.h? Is it still available
> on FreeBSD? Thanks.
Julian added it for TRW Financial Services; the first public
reference machine for 386BSD (which later became FreeBSD and
NetBSD) was ref.tfs.com. TRW supported a lot of the
Hello, I'll go ahead and apologize if this question has already been
answered, but I didn't find anything in the list archive, but I was spelunking through
the source tree and i noticed the following comment in sys/sys/sysent.h:
/* placeholder till we integrate rest of lite2 syscallar
> On Mon, Sep 03, 2001 at 12:04:45PM +0200, Gunnar Olsson wrote:
>> Hi,
>>
>> To increase number of xterms I thought.
>> only the option MAXCONS could be changed.
>> But even though I change it from 16 to 32,
>> I still only get 16.
>>
>> Someone there who can give me I quick answer?
> I thi
> "Peter" == Peter Pentchev <[EMAIL PROTECTED]> writes:
Peter> On Mon, Sep 03, 2001 at 12:04:45PM +0200, Gunnar Olsson wrote:
>> Hi,
>>
>> To increase number of xterms I thought. only the option MAXCONS
>> could be changed. But even though I change it from 16 to 32, I
>> still only get 16.
I've got a promise ATA-66 controller. According to it's bios screen,
the hard drives attached to it are UDMA-4 and the two CD-type devices
are UDMA-2. All four devices are attached with ATA-66 cabling. I
also have "hw.ata.atapi_dma=1" in loader.conf.
I get the following probe:
ad6: 39266MB [
On Mon, Sep 03, 2001 at 06:01:04PM -0600, Ronald G Minnich wrote:
> you do know that API just layed off (almost) all their alpha people,
> right?
>
> alpha is dead. Thank compaq any time.
>
> ron (who owns 112 Compaq Alpha boxes, and 16 API CS20s)
No I didn't. That's really sad.
--
Leo Bickn
On Mon, 3 Sep 2001 [EMAIL PROTECTED] wrote:
> > While not Intel, I understand the Alpha port is coming along nicely:
> >
> > http://www.api-networks.com/products/up1000-board.shtml
> > http://www.api-networks.com/products/up1100-board.shtml
> > http://www.api-networks.com/products/up2000-board
On Mon, Sep 03, 2001 at 02:04:08PM -0700, Kris Kennaway wrote:
> On Sun, Sep 02, 2001 at 10:22:14AM -0700, David O'Brien wrote:
>
> > > --- /dev/null Sat Sep 1 01:13:34 2001
> > > +++ zopen.c Sat Sep 1 01:10:14 2001
> > > @@ -0,0 +1,39 @@
> > > +/*
> > > + * Public domain stdio wrappe
You should really send this to [EMAIL PROTECTED] (Cc'd). Filing a -PR is a good
thing too, as you can always refer to the -PR number in any mail to the
list.
Joe
On Mon, Sep 03, 2001 at 03:43:41PM -0600, Stephen Hurd wrote:
> I've had a problem with my DSL connection for some time now, the brid
Cool, I'll try to get this in later tonight, thanks for taking
the time to do this.
As far as methodology, filing a PR then bringing up on the lists
if it goes unresolved for a couple of days is the prefered method.
* Stephen Hurd <[EMAIL PROTECTED]> [010903 16:39] wrote:
> I've had a problem wi
I've had a problem with my DSL connection for some time now, the bridging they
use appears to forward arp responses AND respond to arp requests. This ends up
filling my log with:
Sep 3 15:17:57 tw2 /kernel: arp: 216.13.207.2 moved from 00:06:29:d5:04:c7 to
00:10:b5:4f:d1:1a on rl0
Sep 3 15:17:
On Sun, Sep 02, 2001 at 10:22:14AM -0700, David O'Brien wrote:
> > --- /dev/null Sat Sep 1 01:13:34 2001
> > +++ zopen.c Sat Sep 1 01:10:14 2001
> > @@ -0,0 +1,39 @@
> > +/*
> > + * Public domain stdio wrapper for libz, written by Johan Danielsson.
> > + */
>
> Can we add this to libz or
> I tested your patch and it solved our problem 100%. There's no
> timedrift anymore.
>
> Do you think the patch will make it in 4.4R. ? We need it urgently.
I can confirm the solution to the time drift problem. Our Netfinity
5600 SMP servers with Serverworks LE chipset now stay nicely in sync.
Katsushi Kobayashi wrote:
>
> I have uploaded the updated driver at:
>
> ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-bsd-5.0-20010903
>
> Note that this driver is an as-is basis code, so there is no document for
> users. Although the kernel patch includes a file
Julian Elischer wrote:
>
> Katsushi Kobayashi wrote:
> >
> > I have uploaded the updated driver at:
> >
> > ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-bsd-5.0-20010903
>
> This url fails for me..
found it at:
ftp://ftp.uec.ac.jp/pub/firewir
Katsushi Kobayashi wrote:
>
> I have uploaded the updated driver at:
>
> ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-bsd-5.0-20010903
This url fails for me..
>
>
--
++ __ _ __
| __--_|\ Julian Elischer |
In a message dated 09/03/2001 10:49:30 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> While not Intel, I understand the Alpha port is coming along nicely:
>
> http://www.api-networks.com/products/up1000-board.shtml
> http://www.api-networks.com/products/up1100-board.shtml
> http://ww
> Hmm, what you should try is change pci reg 0x76 of the K?133 chip, that is
> most likely on pci0:0:0. Then using pciconf set bit 5 to 0 and bit 4 to 1,
> the other bits should be left untouched. Does that help ? if not you
> are probably having another problem
>
> -Søren
Could I beg of you
It seems Jeremiah Gowdy wrote:
> I noticed the following thread about the Via chipset problem. I run a
> production server off a Tyan Tiger 133A, which also has this problem. Tyan
> does not have a BIOS fix, nor does it look like they ever will. When you
> contact them, they point to the Window
The following is from namei.h, around line 116 in -current (r1.30):
/*
* Namei parameter descriptors.
*
* SAVENAME may be set by either the callers of namei or by VOP_LOOKUP.
* If the caller of namei sets the flag (for example execve wants to
*
I noticed the following thread about the Via chipset problem. I run a
production server off a Tyan Tiger 133A, which also has this problem. Tyan
does not have a BIOS fix, nor does it look like they ever will. When you
contact them, they point to the Windows driver fix. They don't seem to
under
I have uploaded the updated driver at:
ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-bsd-5.0-20010903
Note that this driver is an as-is basis code, so there is no document for
users. Although the kernel patch includes a file name as "sbp.c", this
code does not support any fir
On Mon, Sep 03, 2001 at 10:42:57AM -0400, [EMAIL PROTECTED] wrote:
> Which MBs have you found/tested with 64bit PCI busses?
While not Intel, I understand the Alpha port is coming along nicely:
http://www.api-networks.com/products/up1000-board.shtml
http://www.api-networks.com/products/up1100-bo
In a message dated 9/1/01 8:41:58 PM Eastern Daylight Time, [EMAIL PROTECTED]
writes:
> The new P4s are shipping with 800mhz RAMBUS memory modules. Wouldn't 2GB of
> 800mhz RAM go a long way to evening out the performance between a
PC/FreeBSD
> box and all but the most specialized, packet-pus
This might be a dumb question, but if a fix exists in the linux world,
should there not be code available? If so, could this code be integrated
(by someone far more skillful than yours truly) into a future release?
Cheers,
- Original Message -
From: "Albert D. Cahalan" <[EMAIL PROTECTED]
On Mon, Sep 03, 2001 at 12:04:45PM +0200, Gunnar Olsson wrote:
> Hi,
>
> To increase number of xterms I thought.
> only the option MAXCONS could be changed.
> But even though I change it from 16 to 32,
> I still only get 16.
>
> Someone there who can give me I quick answer?
I think this is the
Hi,
To increase number of xterms I thought.
only the option MAXCONS could be changed.
But even though I change it from 16 to 32,
I still only get 16.
Someone there who can give me I quick answer?
Best Regards,
Gunnar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-h
41 matches
Mail list logo
