> Danny Braniss wrote:
> > you might have a point, but this started when I asked why, two
> > boxes, under similar test gave idential real times, but very different
> > user times.
>
> Right, and the answer was: One box has a much faster CPU,
> so it's user time is smaller, but buildworld isn'
John Baldwin wrote:
On Thursday 21 September 2006 14:12, Intron is my alias on the Internet wrote:
Please have a look at the function linker_reference_module() in
/sys/kern/kern_linker.c of 7.0-CURRENT. If the module is loaded on demand,
why not increase its reference counter after loading? In
On Thursday 21 September 2006 14:12, Intron is my alias on the Internet wrote:
> Please have a look at the function linker_reference_module() in
> /sys/kern/kern_linker.c of 7.0-CURRENT. If the module is loaded on demand,
> why not increase its reference counter after loading? In my opinion,
> link
Danny Braniss wrote:
> you might have a point, but this started when I asked why, two
> boxes, under similar test gave idential real times, but very different
> user times.
Right, and the answer was: One box has a much faster CPU,
so it's user time is smaller, but buildworld isn't purely
CPU-b
2006/9/21, Robert Watson <[EMAIL PROTECTED]>:
What are you trying to do, exactly?
The idea is the following: I have a module which replaces the "socket"
system call with my own "extended" socket syscall which adds some
restrictions for "socket" callers. After my module is kldloaded - some
pr
Please have a look at the function linker_reference_module() in
/sys/kern/kern_linker.c of 7.0-CURRENT. If the module is loaded on demand,
why not increase its reference counter after loading? In my opinion,
linker_reference_module() behaves differently from linker_load_file().
--
On Thu, 21 Sep 2006, Maxim Konovalov wrote:
[...]
you're interested only in closing TCP sockets, then the existing tcpkill
command may well do what you want.
It's tcpdrop(8).
Er, yes, so it is.
Thanks :-).
Robert N M Watson
Computer Laboratory
University of Cambridge
[...]
> you're interested only in closing TCP sockets, then the existing tcpkill
> command may well do what you want.
It's tcpdrop(8).
--
Maxim Konovalov
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hac
On Wed, 20 Sep 2006, Taras Danko wrote:
I need to find and close a certain socket from kernel module. My current
implementation iterates over the "allproc" list and checks every process'
file descriptors list to find needed socket. But maybe there is an easier
way to do this? Some nixes have
[...]
> But when you perform the buildworld several times (as you
> should do when you're benchmarking properly), everything
> is already in the RAM disk. If you instead rely on caching
> but you don't have enough RAM to hold all of src + obj +
> toolchain in RAM, then src (or at least parts of it
Eric Anderson wrote:
> Oliver Fromme wrote:
> > Dmitry Morozovsky wrote:
> > > > Because buildworld is I/O-bound on systems with sufficiently
> > > > fast processors.
> > > >
> > > > Try putting the contents of /usr/src into a RAM disk and
> > > > repeat the benchmark. The numbers might lo
11 matches
Mail list logo
