On Mon, Aug 14, 2017 at 07:12:03PM -0400, Jeremie Courreges-Anglas wrote:
>
> This one fell through the cracks...
>
> On Sat, Aug 12 2017, Florian Obser wrote:
> > Stop supporting prefix lifetimes that decrement in real time.
> > It complicates the code, it's off by default
On Mon, Aug 14, 2017 at 10:26:48PM -0400, Jeremie Courreges-Anglas wrote:
>
> So I tinkered with the way ksh(1) tracks memory allocation, trying to
> make it faster in the general case. One approach used a RB tree,
> I wrote since a simple hash table implementation which seems to work
> rather
On Mon, Aug 14 2017, Rob Pierce wrote:
> ifstated currently tracks and maintains the index of each monitored interface
> and does not maintain interface names. This means we need to re-index on
> interface departure and arrival.
>
> The following diff moves away from indexes to
ifstated currently tracks and maintains the index of each monitored interface
and does not maintain interface names. This means we need to re-index on
interface departure and arrival.
The following diff moves away from indexes to names. Indexes are still required,
but easily obtained dynamically
So I tinkered with the way ksh(1) tracks memory allocation, trying to
make it faster in the general case. One approach used a RB tree,
I wrote since a simple hash table implementation which seems to work
rather well.
But the actual problem I'd first like to solve is a corner case. I use
This one fell through the cracks...
On Sat, Aug 12 2017, Florian Obser wrote:
> Stop supporting prefix lifetimes that decrement in real time.
> It complicates the code, it's off by default and RFC 4861 section
> 6.2.1 lists it as MAY.
> After this we can stop regenerating
On 14/08/17(Mon) 22:32, Mark Kettenis wrote:
> > Date: Mon, 14 Aug 2017 16:06:51 -0400
> > From: Martin Pieuchot
> >
> > I'd like to improve the fairness of the scheduler, with the goal of
> > mitigating userland starvations. For that the kernel needs to have
> > a better
Ted Unangst wrote:
> Martin Pieuchot wrote:
> > I'd like to improve the fairness of the scheduler, with the goal of
> > mitigating userland starvations. For that the kernel needs to have
> > a better understanding of the amount of executed time per task.
> >
> > The smallest interval currently
Martin Pieuchot wrote:
> I'd like to improve the fairness of the scheduler, with the goal of
> mitigating userland starvations. For that the kernel needs to have
> a better understanding of the amount of executed time per task.
>
> The smallest interval currently usable on all our architectures
On 14/08/17 21:18, Mark Kettenis wrote:
>> So tracing through HME register writes it seems the difference between
>> OpenBSD and the other OSs is that OpenBSD appears to write to the
>> virtual address 0x40008098000 with a standard (0x80) primary ASI,
>> whereas the other OSs seem to write
> Date: Mon, 14 Aug 2017 16:06:51 -0400
> From: Martin Pieuchot
>
> I'd like to improve the fairness of the scheduler, with the goal of
> mitigating userland starvations. For that the kernel needs to have
> a better understanding of the amount of executed time per task.
>
>
> From: Mark Cave-Ayland
> Date: Mon, 14 Aug 2017 19:59:55 +0100
>
> On 14/08/17 14:25, Mark Kettenis wrote:
>
> >> Great, thanks for the information - the fact that the nsphy0 has been
> >> detected correctly means that the access still works. Looks like I'll
>
I'd like to improve the fairness of the scheduler, with the goal of
mitigating userland starvations. For that the kernel needs to have
a better understanding of the amount of executed time per task.
The smallest interval currently usable on all our architectures for
such accounting is a tick.
On Mon, Aug 14, 2017 at 05:53:10PM +, Florian Obser wrote:
> After we stopped processing router advertisements in the kernel
> sppp_update_ip6_addr() became the last user of n6_are_prefix_equal().
> Since it compares /128 prefixes it doesn't need all the bells and
> whistles and can be
On Mon, Aug 14, 2017 at 11:21:03AM -0400, Ted Unangst wrote:
> Klemens Nanni wrote:
> > > + case 'z':
> > > + autoaction = AUTO_SUSPEND;
> > > + autolimit = strtonum(optarg, 1, 100, );
> > > + if (errstr != NULL)
> > > +
On 14/08/17 14:25, Mark Kettenis wrote:
>> Great, thanks for the information - the fact that the nsphy0 has been
>> detected correctly means that the access still works. Looks like I'll
>> have to go digging deeper.
>
> The OpenBSD code uses %asi if necessary to let the hardware do the
>
After we stopped processing router advertisements in the kernel
sppp_update_ip6_addr() became the last user of n6_are_prefix_equal().
Since it compares /128 prefixes it doesn't need all the bells and
whistles and can be converted to a memcmp. Remove the new unused
n6_are_prefix_equal().
OK?
On 2017/08/14 16:48, Simon Mages wrote:
> Hi,
>
> you may want to take a look into /etc/login.conf
> login.conf(5), cap_mkdb(1)
I wouldn't normally recommend cap_mkdb for the login.conf file, it's too
easy to forget to update the db after making a change. I'd just edit the
text file.
You will
On 14.8.2017. 16:48, Simon Mages wrote:
> Hi,
>
> you may want to take a look into /etc/login.conf
> login.conf(5), cap_mkdb(1)
>
> In this file you can fiddle with you limit maxima
> for login classes.
>
> BR
> Simon
>
Thank you, i will do that ...
Klemens Nanni wrote:
> > + case 'z':
> > + autoaction = AUTO_SUSPEND;
> > + autolimit = strtonum(optarg, 1, 100, );
> > + if (errstr != NULL)
> > + error("invalid percent: %s", errstr);
> > +
On Sun, Aug 13, 2017 at 02:13:42PM +0200, Jesper Wallin wrote:
> On Sun, Aug 13, 2017 at 09:52:22AM +0200, Martijn van Duren wrote:
> > I've also been bitten by this a couple of times, but you can also solve
> > this via the sensorsd framework, which is how I've done it.
>
> Yeah, someone on IRC
Hi,
you may want to take a look into /etc/login.conf
login.conf(5), cap_mkdb(1)
In this file you can fiddle with you limit maxima
for login classes.
BR
Simon
2017-08-14 16:28 GMT+02:00, Hrvoje Popovski :
> On 14.8.2017. 16:03, Alexander Bluhm wrote:
>> On Mon, Aug 14, 2017 at
On 14.8.2017. 16:03, Alexander Bluhm wrote:
> On Mon, Aug 14, 2017 at 03:52:56PM +0200, Hrvoje Popovski wrote:
>> # netstat -rnf inet
>> netstat: Cannot allocate memory
>
> Have you tried to increase ulimit -d ?
it seems that i can decrease it but not increase it, or i don't know how
to do it
On Mon, Aug 14, 2017 at 03:52:56PM +0200, Hrvoje Popovski wrote:
> # netstat -rnf inet
> netstat: Cannot allocate memory
Have you tried to increase ulimit -d ?
bluhm
Hi all,
when openbsd imports cca 1M routes or more and if i want to see them
with "netstat -rn" i'm getting "Cannot allocate memory". bgpd can see
all routes. i don't think that this is real problem but full bgp table
is cca 700K routes.
# bgpctl show ip bgp mem
RDE memory statistics
1245184
> From: Mark Cave-Ayland
> Date: Mon, 14 Aug 2017 06:31:34 +0100
>
> On 13/08/17 16:52, Kaashif Hymabaccus wrote:
>
> > Hello Mark,
> >
> > I have a Sun Ultra 5 with the following dmesg:
> >
> > console is /pci@1f,0/pci@1,1/ebus@1/se@14,40:a
> > Copyright
On Sun, Aug 13, 2017 at 11:03:02PM -0400, Ted Unangst wrote:
> here's a new version that pulls the check higher.
OK bluhm@
> - if (so->so_type == SOCK_SEQPACKET)
> - flags = MSG_EOR;
> - else
> - flags = 0;
> + flags = 0;
>
> error = sosend(so,
This diff makes iwm_stop() always run in a process context.
I want iwm_stop() to be able to sleep so that it can wait for asynchronous
driver tasks, and perhaps even wait for firmware commands, in the future.
If the interrupt handler detects a fatal condition, instead of calling
iwm_stop()
On 14/08/17 01:40, Christian Weisgerber wrote:
Jonathan Matthew:
Better version that actually preserves the port command register state across
resets, rather than throwing it away and replacing it with garbage:
This appears to break ahci on the OverDrive 1000:
...
ahci0 at simplebus0: AHCI
29 matches
Mail list logo