Apologies for the cross post. Were trying out the ofed code and running
into some issues, so would love to discuss.
-vijay
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mai
On Fri, 10 May 2013 13:43:47 +0200
Uffe Jakobsen wrote:
> On 2013-05-10 12:11, Alexander Leidinger wrote:
> >
> > I worry about what is going on. We have something which is supposed
> > to provide security as required, but is does not seem to work as
> > described. We either need to fix the docum
On 5/10/13 12:31 PM, Karl Dreger wrote:
Hello,
I have been taking a look at a few syscalls in /usr/src/sys/kern/ and
always find that in their actuall c definition the function names are
preprended by a sys_. Take for example the fork system call which
is found in /usr/src/sys/kern/kern_fork.c
i
Hello,
I have been taking a look at a few syscalls in /usr/src/sys/kern/ and
always find that in their actuall c definition the function names are
preprended by a sys_. Take for example the fork system call which
is found in /usr/src/sys/kern/kern_fork.c
int
sys_fork(struct thread *td, struct fork
On 2013-05-10 12:11, Alexander Leidinger wrote:
I worry about what is going on. We have something which is supposed to
provide security as required, but is does not seem to work as
described. We either need to fix the documentation, or a bug in the
code. To do the later it needs to be debugged
On Thu, 09 May 2013 15:24:46 -0500
Joshua Isom wrote:
> If you're just doing virtualization and not worrying about security,
I worry about what is going on. We have something which is supposed to
provide security as required, but is does not seem to work as
described. We either need to fix the
6 matches
Mail list logo
