Date: Tue, 9 Sep 2014 15:10:46 +1000
From: David Gwynne da...@gwynne.id.au
mpsafe mpi. eyes would be appreciated. tests well to me.
ok?
Tested on
mpi0 at pci5 dev 0 function 0 Symbios Logic SAS1064E rev 0x02: msi
Couldn't find any problems in the code, so
ok kettenis@
Index:
Hi,
I have improved my amd64 pmap patches a bit and finally got around to
doing some benchmarks with them.
Systems:
- core-i7 is an Intel Core i7-860 with 4 cores / 8 threads
- core2duo is an Intel Core 2 Duo T8100 with 2 cores
- KVM is a VM with 4 vcpus running on qemu 2.1/Linux 3.16 on the
Simple cleanups for amd64 pmap
- use __func__ in panics/printfs (fixes some out of sync function names)
- tell the compiler that code paths where we print diagnostics are
unlikely
- use pmap_valid_entry() in some places
- KERNSPACE is not used anywhere
diff --git
Optimize pmap on amd64
based on a patch for i386 by Art from 2008 that removes the APTE stuff.
Some additional bits were taken from a patch by Art for amd64 from 2005.
Instead of mapping the ptes of an inactive pmap in the APTE range, and
then doing an unconditional remote TLB-flush on all
On Sun, Sep 14, 2014 at 02:54:54PM +0200, Stefan Fritsch wrote:
I would like people to test the diffs on other machines. In particular on
non-Intel CPUs. The only AMD system I could get hold of did not run
reliably with openbsd even without the pmap diff.
I tested MP 'kernel -j 2' on a PC
On Sun, 14 Sep 2014, Job Snijders wrote:
On Sun, Sep 14, 2014 at 02:54:54PM +0200, Stefan Fritsch wrote:
I would like people to test the diffs on other machines. In particular on
non-Intel CPUs. The only AMD system I could get hold of did not run
reliably with openbsd even without the
Results for an old Athlon (hmm, I don't remember it running at 10.8 Ghz
before)
cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, 10823.06 MHz
forktest 0m19.23s real 0m0.72s user 0m22.46s system
forktest+0m16.33s real 0m0.50s user 0m18.22s system
kernel -j2
On Sun, Sep 14, 2014 at 06:54:40PM +0200, Stefan Fritsch wrote:
On Sun, 14 Sep 2014, Job Snijders wrote:
I tested MP 'kernel -j 2' on a PC Engines apu1c4 (AMD G series T40E, 1
GHz dual Bobcat core with 64 bit support) and saw no speedup.
Thanks. But no slowdown either?
No slowdown either.
On Sunday 14 September 2014 12:13:44, Brent Cook wrote:
Results for an old Athlon (hmm, I don't remember it running at 10.8
Ghz before)
cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, 10823.06 MHz
forktest 0m19.23s real 0m0.72s user 0m22.46s system
forktest+0m16.33s
On Mon, Sep 01, 2014 at 08:52:49PM +0600, Alexandr Shadchin wrote:
Hi,
This diff updates xkeyboard-config to the latest release 2.12.
Also includes diff from http://marc.info/?l=openbsd-techm=140750210214198w=2
Tested on amd64 and i386.
Comments ? OK ?
Sorry for beeing late. ok matthieu@
On Sun, Sep 14, 2014 at 08:07:17PM +0200, Stefan Fritsch wrote:
On Sunday 14 September 2014 12:13:44, Brent Cook wrote:
Results for an old Athlon (hmm, I don't remember it running at 10.8
Ghz before)
cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, 10823.06 MHz
forktest 0m19.23s real
Hi,
When I put a CF to PCCard adapter (not CardBus) in my laptop to work on a CF
boot image, I was surprised by this kernel message :
** wdc2 at pcmcia0 function 0 SanDisk, SDP, 5/3 0.6: can't handle card info
And the card was not working at all, as weren't any other PCCard I tried
Date: Sun, 14 Sep 2014 23:57:09 +0200
From: Thierry Deval thierry+openbsd.t...@deval.be
Hi,
When I put a CF to PCCard adapter (not CardBus) in my laptop to work on a CF
boot image, I was surprised by this kernel message :
** wdc2 at pcmcia0 function 0 SanDisk, SDP, 5/3 0.6: can't
Hi,
Todd C. Miller wrote on Fri, Sep 12, 2014 at 09:23:31AM -0600:
On Thu, 11 Sep 2014 22:03:04 -0700, William Orr wrote:
I'm resubmitting this patch since the source tree was locked last time I
submitted. Any thoughts?
I think we've discussed this one to death already. It looks fine
to
The attack in the last link is on lattices over an ideal, which are related to
but not the same as NTRU lattices. It's not clear how to extend it to the NTRU
lattice. It's also not clear that, if extended, it would significantly improve
on the best currently known attack on NTRU: that attack
The following mails will contain patchs that implement the VPLS datapath
in OpenBSD. Applying all patchs should allow people to configure a
network using VPLS manually.
The first patch prepares the system sources to receive the wire
implementation: it turns some mpe specific code into some
The following patch is just a preparation for the code that is coming to
implement the wire network interface (the VPLS datapath) to work on OpenBSD.
This code turns the mpe code that handles route and labels into some general
use functions that will be called by mpe and wire.
diff --git
The following patch implements the basics of the wire network interface.
diff --git sys/conf/GENERIC sys/conf/GENERIC
index 309528e..444dcbe 100644
--- sys/conf/GENERIC
+++ sys/conf/GENERIC
@@ -95,6 +95,7 @@ pseudo-device systrace 1 # system call tracing device
# clonable devices
Adds support for wire configuration and status printing.
diff --git sbin/ifconfig/ifconfig.c sbin/ifconfig/ifconfig.c
index 133ff55..3a363ff 100644
--- sbin/ifconfig/ifconfig.c
+++ sbin/ifconfig/ifconfig.c
@@ -122,6 +122,10 @@ struct sockaddr_in netmask;
#ifndef SMALL
struct
We use async-signal-safe (not async-signal safe) elsewhere,
and so does POSIX.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/sigaction.html
Index: sigaction.2
===
RCS file: /cvs/src/lib/libc/sys/sigaction.2,v
retrieving
20 matches
Mail list logo
