On 12/11/2007, Randall Hyde <[EMAIL PROTECTED]> wrote:
> At this point I'm not sure why FreeBSD's API call is so slow (btw, it's not
> the system call that's responsible, if I make several additional API calls
> on each read, e.g., doing lseeks, this has only a marginal impact on
> performance). B
On Sun, Nov 11, 2007 at 09:52:21AM -0800, Randall Hyde wrote:
>why C's code was so much faster, I dug into the source code and discovered
>that open/read/write/etc. use *buffered* I/O (which explains why "dd"
>performs so well).
open/read/write/etc. do _not_ do any buffering in userland. This is
Randall Hyde wrote:
> Hi All,
>
> I recently ported my HLA (High Level Assembler) compiler to FreeBSD and,
> along with it, the HLA Standard Library. I have a performance-related
> question concerning file I/O.
>
> It appears that character-at-a-time file I/O is *exceptionally* slow. Yes, I
> rea
We installed a 5.3-RELEASE box back in 2004, and it's been running
pretty hard ever since with no crashes, reboots or anything. We're
about to finally take it down to upgrade the OS soon - are there any
stats anyone wants to see before we do? I know in the past there have
been some "I won
On Mon, 12 Nov 2007, 04:08-0600, Kevin Day wrote:
>
> We installed a 5.3-RELEASE box back in 2004, and it's been running
> pretty hard ever since with no crashes, reboots or anything. We're
> about to finally take it down to upgrade the OS soon - are there any
> stats anyone wants to see before we
>
>
> Hello Randy,
>
> First, let me out myself as a fan of yours. It was your book that got me
> started on ASM and taught me a lot about computers and logic, plus it
> provided some entertainment and mental sustenance in pretty boring
> times, so thanks!
>
> Now, as for your problem: I think I h
I am looking for functionality similar to Linux's /proc//fd/.
I need to know what is the file name of an open file descriptor.
/proc//fd is missing on FreeBSD.
There's something called 'fdescfs'. In /dev/fd/ it shows the list of file
descriptors. But they don't seem to be symbolic links to open f
mbolic links to open files. And
> > also it only shows FDs of the current process.
> >
> > So why there's no /proc//fd in FreeBSD? And how do I work around this?
>
> > Or should I just invest time and write a kernel patch implementing
> > /proc//fd/?
>
> You
e these patches a try:
http://www.watson.org/~robert/freebsd/20071112-procstat.tgz
They reflect a work-in-progress procstat(1) tool, which inspects process state
in various ways. They are developed against 8-CURRENT, but likely still apply
fairly easily to 7-STABLE. They suffer various deficie
to show the the same information instead of the specialized
utility.
Thanks,
Yuri
Quoting Robert Watson <[EMAIL PROTECTED]>:
> You can give these patches a try:
>
>http://www.watson.org/~robert/freebsd/20071112-procstat.tgz
>
> They reflect a work-in-progress proc
//fd in FreeBSD? And how do I work around this?
Or should I just invest time and write a kernel patch implementing
/proc//fd/?
You can give these patches a try:
http://www.watson.org/~robert/freebsd/20071112-procstat.tgz
They reflect a work-in-progress procstat(1) tool, which inspects
On Mon, 12 Nov 2007, Yuri wrote:
I looked at the patch. It retrieves file description information through
'sysctl' calls with proprietary keys.
Isn't it better architecturally to expose the same information through
procfs interface? At least from the filesystem level and up standard tools
l
On Mon, 12 Nov 2007, Yuri wrote:
Y> I looked at the patch. It retrieves file description information through
Y> 'sysctl' calls with proprietary keys.
Y>
Y> Isn't it better architecturally to expose the same information through procfs
Y> interface? At least from the filesystem level and up standar
On Mon, 12.11.2007 at 04:08:45 -0600, Kevin Day wrote:
> ts1# vmstat -m
>
> Type InUse MemUse HighUse Requests Size(s)
>allocindir12 1K 2623K532365228 64
>newblk 1 1K 1K602736113 64,256
> NFSV3 srvdesc 0 0K 2K107739750 16,256
>
On Mon, 12 Nov 2007, Maxim Konovalov wrote:
On Mon, 12 Nov 2007, 04:08-0600, Kevin Day wrote:
We installed a 5.3-RELEASE box back in 2004, and it's been running
pretty hard ever since with no crashes, reboots or anything. We're
about to finally take it down to upgrade the OS soon - are there
15 matches
Mail list logo
