RE: FAST_IPSEC bug fix

2004-04-24 Thread Oldach, Helge
> From: Sam Leffler [mailto:[EMAIL PROTECTED] > On Apr 24, 2004, at 11:24 AM, Mike Tancsa wrote: > > At 12:56 PM 24/04/2004, Sam Leffler wrote: > >> On Apr 24, 2004, at 9:03 AM, Oldach, Helge wrote: > >> > >>> Hi list, > >>> > >>> this is a month-old mail about the lack of a FAST_IPSEC feature > >

Re: FreeBSD's malloc problem ?

2004-04-24 Thread Anton Alin-Adrian
Daniel Ellard wrote: And let there be light... DANG.. well it almost blinded me. I was confusing with char[16], which has the +1 byte for the null terminating, but the malloc(16) hasn't... No, that's still not quite it... char[16] allocates exactly 16 characters. Period. There's no extra s

Re: FreeBSD's malloc problem ?

2004-04-24 Thread Daniel Ellard
> And let there be light... DANG.. well it almost blinded me. I was > confusing with char[16], which has the +1 byte for the null > terminating, but the malloc(16) hasn't... No, that's still not quite it... char[16] allocates exactly 16 characters. Period. There's no extra space on the end

Re: FreeBSD's malloc problem ?

2004-04-24 Thread Anton Alin-Adrian
Nicolas Rachinsky wrote: * Anton Alin-Adrian <[EMAIL PROTECTED]> [2004-04-24 21:27 +0300]: tmp = (char *) malloc(strlen(s)); // line 68 Hmm, you need strlen(s)+1 bytes to store the string -- don't forget the trailing null byte. Nicolas And let there be light... DANG.. well it almost blinded me.

Re: FreeBSD's malloc problem ?

2004-04-24 Thread Nicolas Rachinsky
* Anton Alin-Adrian <[EMAIL PROTECTED]> [2004-04-24 21:27 +0300]: > tmp = (char *) malloc(strlen(s)); // line 68 Hmm, you need strlen(s)+1 bytes to store the string -- don't forget the trailing null byte. Nicolas ___ [EMAIL PROTECTED] mailing list

FreeBSD's malloc problem ?

2004-04-24 Thread Anton Alin-Adrian
Hello hackers ! Before anything else, I must mention I am running FreeBSD 4.9-RELEASE, and that is the OS where I encounter the problem. I was developing some functions fooling around for parsing some bigger opensource project's config file and look what happened: There are many functions i

Re: FAST_IPSEC bug fix

2004-04-24 Thread Mike Tancsa
At 12:56 PM 24/04/2004, Sam Leffler wrote: On Apr 24, 2004, at 9:03 AM, Oldach, Helge wrote: Hi list, this is a month-old mail about the lack of a FAST_IPSEC feature compared to legacy IPSEC. Including a working patch. I haven't seen this being committed, or is it? Please also MFC to STABLE. The

Re: device pooling and high interrupts

2004-04-24 Thread Mike Silbersack
On Sat, 24 Apr 2004, GiZmen wrote: > Hello, > > I am runnign freebsd 5.2.1 on 386 arch with two rl lan cards. My mainboard > is on VIA KT 266A with AMD athlon 1.1. > I read man polling and i have HZ=1000. My problem is that when i set up > sysctl variable kern.polling.enable=1 my interrupts great

Re: device pooling and high interrupts

2004-04-24 Thread Dmitry Morozovsky
On Sat, 24 Apr 2004, GiZmen wrote: G> I am runnign freebsd 5.2.1 on 386 arch with two rl lan cards. My mainboard G> is on VIA KT 266A with AMD athlon 1.1. G> I read man polling and i have HZ=1000. My problem is that when i set up G> sysctl variable kern.polling.enable=1 my interrupts greatly incre

device pooling and high interrupts

2004-04-24 Thread GiZmen
Hello, I am runnign freebsd 5.2.1 on 386 arch with two rl lan cards. My mainboard is on VIA KT 266A with AMD athlon 1.1. I read man polling and i have HZ=1000. My problem is that when i set up sysctl variable kern.polling.enable=1 my interrupts greatly increase. When my system is idle and indicate

RE: FAST_IPSEC bug fix

2004-04-24 Thread Oldach, Helge
Hi list, this is a month-old mail about the lack of a FAST_IPSEC feature compared to legacy IPSEC. Including a working patch. I haven't seen this being committed, or is it? Please also MFC to STABLE. Regards, Helge > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTE

Re: bad news for bsdtar..

2004-04-24 Thread Richard Coleman
Alfred Perlstein wrote: Threads are pretty portable these days, obviously making it a compile time option could work, but then again performance would be nice and it is _our_ tar. ;) Also, unless you mean 'aio' or 'another process' by "non-blocking/async IO" then I'm pretty sure you are wrong, a

Re: bad news for bsdtar..

2004-04-24 Thread Alfred Perlstein
* Alexey Dokuchaev <[EMAIL PROTECTED]> [040424 03:14] wrote: > On Sat, Apr 24, 2004 at 01:59:13AM -0700, Alfred Perlstein wrote: > > > > Have you guys thought of using aio or at least another process > > to parallelize IO? (One to read files, and one to write out the > > archive) > > > > Actuall

RE: how to flush out cache.?

2004-04-24 Thread Jan Mikkelsen
Julian Elischer wrote: > Other than reading a few GB of data, is there a way to flush > out the cache copy of a file I've written? I don't know how this will fit into your application, but unmounting and remounting the filesystem is a way that springs to mind. Perhaps not as isloated as you'd lik

Re: netgraph ability

2004-04-24 Thread Ruslan Ermilov
[ Redirected to -net ] On Thu, Apr 22, 2004 at 05:50:57PM -0700, David Yeske wrote: > I'm in a situation where I need to emulate multiple ethernet devices with > different mac addresses. I have gotten far enough to have this. > > I ran ngctl and then ran > "mkpeer . eiface hook ether" > > I the