Re: Checkpointing of simple programs in FreeBSD

2012-03-19 Thread K. Macy
Take a look at gcore. That will let you checkpoint memory mappings and registers. The dragonfly implementation also keeps track of the sbrk value and open file handles which you will need to handle separately. Restoring the mappings and register state should be straightforward. I'm not sure at how

Re: interface for import/export flowtable

2012-01-11 Thread K. Macy
On Sat, Jul 24, 2010 at 2:17 PM, Bjoern A. Zeeb wrote: > On Thu, 22 Jul 2010, alan yang wrote: > > Hey, > > >> Wonder people had implemented interface to import / export flowtable. > Yes I did, and I added an API to query it more generally. I didn't add it to net/flowtable.c because my usage seem

Re: buf_ring(9) API precisions

2011-09-24 Thread K. Macy
You're right. A write memory barrier is needed there. Thanks On Thu, Sep 22, 2011 at 12:43 AM, Arnaud Lacombe wrote: > Hi, > > On Mon, Sep 19, 2011 at 8:46 AM, K. Macy wrote: >> If the value lags next by one then it is ours. This rule applies to >> all callers so t

Re: buf_ring(9) API precisions

2011-09-19 Thread K. Macy
If the value lags next by one then it is ours. This rule applies to all callers so the rule holds consistently. On Mon, Sep 19, 2011 at 5:53 AM, Arnaud Lacombe wrote: > Hi, > > On Fri, Sep 16, 2011 at 10:41 AM, K. Macy wrote: >> On Fri, Sep 16, 2011 at 3:02 AM, Arnaud Lacombe

Re: buf_ring(9) API precisions

2011-09-16 Thread K. Macy
On Fri, Sep 16, 2011 at 3:02 AM, Arnaud Lacombe wrote: > Hi, > > On Wed, Sep 14, 2011 at 10:53 PM, Arnaud Lacombe wrote: >> Hi Kip, >> >> I've got a few question about the buf_ring(9) API. >> >> 1) what means the 'drbr_' prefix. I can guess the two last letter, 'b' >> and 'r', for Buffer Ring, bu

Re: buf_ring(9) API precisions

2011-09-15 Thread K. Macy
On Thu, Sep 15, 2011 at 4:53 AM, Arnaud Lacombe wrote: > Hi Kip, > > I've got a few question about the buf_ring(9) API. > > 1) what means the 'drbr_' prefix. I can guess the two last letter, 'b' > and 'r', for Buffer Ring, but what about 'd' and 'r' ? DRiver BufRing > 2) in `sys/sys/buf_ring.h',

Re: How to include without "device_if.h" and "bus_if.h"?

2011-09-08 Thread K. Macy
2011/9/8 Lev Serebryakov : > Hello, K.. > You wrote 8 сентября 2011 г., 18:22:11: > >> Just add them to the makefile. They'll be automatically created  as >> dependencies. >  Is it good idea to create these empty files only for one prototype > from ? I can't comment on whether or not it is good or

Re: How to include without "device_if.h" and "bus_if.h"?

2011-09-08 Thread K. Macy
Just add them to the makefile. They'll be automatically created as dependencies. 2011/9/8 Lev Serebryakov : > Hello, Freebsd-hackers. > >  I need to include in my kernel module to use > devctl_notify(). But my module doesn't have device_if.h or bus_if.h, > which are required by . >  What should

Re: dwarf2 reader

2011-06-13 Thread K. Macy
Have you taken a look at lldb? It is designed to be more modular. -Kip On Mon, Jun 13, 2011 at 4:05 PM, Ewart Tempest wrote: > I have developed some flight recording capability in the JUNOS FreeBSD based > kernel, with the flight recorded data being captured in binary form for > performance. A

Re: FreeBSD I/OAT (QuickData now?) driver

2011-06-11 Thread K. Macy
Oops, second 10 GigE should obviously be 1GigE On Tuesday, June 7, 2011, K. Macy wrote: > All 10GigE NICs and some newer 10 GigE NICs have multiple hardware > queues with a separate MSI-x vector per queue, where each vector is > directed to a different CPU. The current operating model i

Re: FreeBSD I/OAT (QuickData now?) driver

2011-06-07 Thread K. Macy
All 10GigE NICs and some newer 10 GigE NICs have multiple hardware queues with a separate MSI-x vector per queue, where each vector is directed to a different CPU. The current operating model is to have a separate interrupt thread per vector. This obviously gets bogged down if one has multiple card

Re: sysv semaphore

2002-02-11 Thread k Macy
Look at the posix shmem and sem functions: shm_open shm_unlink sem_open, sem_close, sem_post etc. --- Matthew <[EMAIL PROTECTED]> wrote: > Is there a sysv semphore/shmem implementation using > mmap available for FreeBSD? I need a userland > based sysv > sem/shm library to write a little project,

Re: to users of threads (GDB support)

2002-02-11 Thread k Macy
See my page now. It contains a pointer to a tarball with what I believe to be the appropriate style patches and a single unified diff. I'm obviously new to this so humor me and let me know if there are any further problems. --- David O'Brien <[EMAIL PROTECTED]> wrote: > On Sun, Feb 10, 2002 at 1

-CURRENT AIO bug Re: How well does EVFILT_AIO work?

2002-01-17 Thread k Macy
It turns that this problem is specific to AIO in -CURRENT. I wrote a simple program that uses the three different completion mechanisms (polling with aio_error, polling with kevent, and using SIGIO) to fill up a file by writing 8kb at a time to the file and then reading 8kb at a time from the fil

How well does EVFILT_AIO work?

2002-01-12 Thread k Macy
Has anybody used AIO in conjunction with kevent? I am seeing as much as a 12 second latency between when I do an 8k aio_write to a file on local disk and kevent returning its completion (I'm calling kevent every ~20ms). Using regular writes works fine, but this is a multi-threaded application so

ptrace bug was Re: gnu/33262: gdb does not handle pending signals correctly when single stepping

2002-01-03 Thread k Macy
Not to mention that SIGVTALRM is already used by the thread library (although I would hope that _thread_sys_sigaction is smart enough to handle that case). I've stepped through the GDB code on both 4.18 and 5.1. On 5.1 I found the following in i386fbsd-nat.c: void child_resume (ptid_t ptid, int

Re: problems with recurring SIGTRAP under gdb

2001-10-29 Thread k Macy
msg = sk_receive(); if((msg->type == SK_SIGNAL_MSG) && (msg->data.l == HARD_SIG_00010)) break; } while (1); sk_remove_poll_fd(slot); } beneath this it just uses poll --- Ian Dowse <[EMAIL PROTECTED]> wrote: > In message > <[EMAIL PROTECTED]

problems with recurring SIGTRAP under gdb

2001-10-28 Thread k Macy
Any idea why when I insert a breakpoint I get a SIGTRAP and can't continue any further? Is this a bug in the FreeBSD distribution's gdb? I don't see this behavior on any other platform that I am using. (Linux/ Solaris/ OSF1) I am only seeing on this particular application. The binary is 60MB d