"Sonja Milicic" <[EMAIL PROTECTED]> wrote
So, could anyone please give me a detailed
explanation of how to open a file in kernel and write to it - best data
types to use, functions, what to look out for, maybe a link to tutorial
or manual that deals with this (if such a thing exists), etc.?
N
John-Mark Gurney wrote:
> no, I was thinking: "x-struct/proc;version=1"... Doesn't mean they
> shouldn't be.. Currently most tools detect different versions of structs
> by examining the size.. This isn't always safe as fields could get
> shuffled or meanings changed w/o changing the size..
I
Ivan Voras wrote this message on Mon, May 07, 2007 at 20:12 +0200:
> John-Mark Gurney wrote:
> > Ivan Voras wrote this message on Mon, May 07, 2007 at 18:39 +0200:
> >> My proposal is to MIME-ify the Format fields, best presented in examples:
> >>
> >> "S,proc" -> "x-struct/proc"
> >> "S,xfile" ->
On Mon, May 07, 2007 at 06:39:34PM +0200, Ivan Voras wrote:
> My proposal is to MIME-ify the Format fields, best presented in examples:
>
> "S,proc" -> "x-struct/proc"
> "S,xfile" -> "x-struct/xfile"
The format field is intended for the interpretation of userland programs
like sysctl. For those f
John-Mark Gurney wrote:
> Ivan Voras wrote this message on Mon, May 07, 2007 at 18:39 +0200:
>> My proposal is to MIME-ify the Format fields, best presented in examples:
>>
>> "S,proc" -> "x-struct/proc"
>> "S,xfile" -> "x-struct/xfile"
>
> If you do, don't forget to add the version of the field t
Eric Anderson wrote:
> How about adding a -m switch to sysctl that outputs the MIME compatible
> format, leaving the other formats unchanged to avoid breaking something
> someone is expecting?
I don't think it's a good idea because it either means adding another
"format-like" field in the kernel
Ivan Voras wrote this message on Mon, May 07, 2007 at 18:39 +0200:
> My proposal is to MIME-ify the Format fields, best presented in examples:
>
> "S,proc" -> "x-struct/proc"
> "S,xfile" -> "x-struct/xfile"
If you do, don't forget to add the version of the field to the
mime-type as these structur
On 05/07/07 11:39, Ivan Voras wrote:
In the output of sysctl -oa I see values like:
kern.proc.all: Format:S,proc Length:75264
Dump:0x00032011fac380d4fec3...
kern.proc.proc_td: Format:N Length:75264
Dump:0x00032011fac380d4fec3...
kern.file: Format:S,xfile Length:18616
Dump
In the output of sysctl -oa I see values like:
kern.proc.all: Format:S,proc Length:75264
Dump:0x00032011fac380d4fec3...
kern.proc.proc_td: Format:N Length:75264
Dump:0x00032011fac380d4fec3...
kern.file: Format:S,xfile Length:18616
Dump:0x34003e0ce8030600...
On 5/7/07, valiy <[EMAIL PROTECTED]> wrote:
Vlad GALU wrote:
> On 5/7/07, valiy <[EMAIL PROTECTED]> wrote:
> [...]
>It might be related to phkmalloc vs jemalloc. You may want to try
> to link against jemalloc to see if the slowdown still occurs.
>
http://lists.freebsd.org/pipermail/freebsd-st
On 5/7/07, valiy <[EMAIL PROTECTED]> wrote:
[...]
It might be related to phkmalloc vs jemalloc. You may want to try
to link against jemalloc to see if the slowdown still occurs.
--
If it's there, and you can see it, it's real.
If it's not there, and you can see it, it's virtual.
If it's there,
FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon Jan 15 14:39:55 MSK
2007 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MY i386
valiy# g++ test_set.cpp
valiy# ./a.out
filling
clearing
done
alloc time 3.783clear time 7.987
valiy# g++34 test_set.cpp
valiy# ./a.out
filling
clearing
done
12 matches
Mail list logo
