well, I am working on writing a capture program to do 640x480x12bpp@30fps
to a raw disk, but writing to the raw device is SOOO slow... the reason
I say it's slow is the fact that it takes 8 times the system time writing
than reading...
a bit about the system... k6/2-250, 100mhz system bus, pc10
{ Moved to FreeBSD-Questions }
Emm, I want your system. Have you double checked your numbers? They
look a bit high. Here's what I get on a vinum stripe across two 'cudas
on an SMP box:
rsnow@basil% time dd if=/dev/vinum/rstripe of=/dev/null bs=64k
count=2048
2048+0 records in
2048+0 records ou
John-Mark, have you double checked your numbers? I get:
rsnow@basil% time dd if=/dev/vinum/rstripe of=/dev/null bs=64k
count=2048
2048+0 records in
2048+0 records out
134217728 bytes transferred in 8.096565 secs (16577120 bytes/sec)
0.016u 0.482s 0:08.09 6.0% 73+370k 0+0io 0pf+0w
On vinum
In article [EMAIL PROTECTED]> you
write:
>well, I am working on writing a capture program to do 640x480x12bpp@30fps
>to a raw disk, but writing to the raw device is SOOO slow... the reason
>I say it's slow is the fact that it takes 8 times the system time writing
>than reading...
>
>a bit about
On Thu, 4 Nov 1999, Arun Sharma wrote:
> On Thu, Nov 04, 1999 at 09:31:02PM -0600, Chris Costello wrote:
> > On Thu, Nov 04, 1999, Arun Sharma wrote:
> > > Can a loadable module, say a network driver register variables with
> > > sysctl ? Can sysctl itself be made a loadable module ? As for the s
On Fri, 5 Nov 1999, Mike Smith wrote:
> > On Thu, 4 Nov 1999, Mike Smith wrote:
> > > Sysctl is faster than kstat once you have performed the name->oid
> > > lookup. There is basically nothing that kstat can do that sysctl can't
> > > do better and faster, apart from lookup-by-name.
> >
> > E
David Malone wrote:
>
> However, procfs currently allows people to do this with an executables
> file. You can make hard links to and run /proc/nnn/file as it is
> essentially another hard link to the executable file. This could
> be a problem if you have suid executables protected by nonexecutab
Borja Marcos wrote:
>
> Hello,
>
> Many security exploits create files in the /tmp directory
> and execute them. I think it would be a good idea to add logging
> to the to exec_check_permissions() in kern.exec.c so that attempts
> to run files from a filesystem mounted as "noexec
8 matches
Mail list logo
