After fighting with this for a couple of weeks I realise there's a race that
hits on faster machines. I'm trying to work backwards now - using the
sched/queue mechanism on spllower on the current implementation to understand
the timing issues better.
It's been an intense week+ with little to sh
On December 15, 2018 10:59:19 AM GMT+05:30, Santhosh Raju
wrote:
>Hello
>
>I noticed that the tests for uvm_hotplug(9) situated under
>tests/sys/uvm/t_uvm_physseg.c was failing build.
>
>The reason for failure was the comparison between psize_t (which is
>defined as unsigned log inside t_uvm_hotp
Hello hackers,
I'm writing to introduce a project I've been working on off-and-on for a
while now - verifying parts of kernel code using a formal specifier[1]
Please find attached a patch to try out a formal verification run of the
Adaptive Replacement Cache by Megido et.al. [2]
You can try it o
Hi,
After some discussion with Jason, and re-reading the code and its
current state in code, I've come to the conclusion that it's in the
interest of brevity to remove everything in sys/kern/ and sys/uvm/ which
implement the "dynamic" part of uvm_hotplug(9).
The top two reasons for this in my min
>>>>> Santhosh Raju writes:
> On Fri, Dec 1, 2023 at 6:42 AM Mathew Cherry G. wrote:
>>
>> Hi,
>>
>> After some discussion with Jason, and re-reading the code and its
>> current state in code, I've come to the conc
Hello,
I'm investigating how to make our kernel less reliant on hardclock(9)
being called at hz(9).
Please find attached a patch to reduce hardclock(9)'s responsibilities
wrt the rest of the system timekeeping.
The idea is that hardclock(9) will drive callout_hardclock() for now,
until we modify
>>>>> Martin Husemann writes:
> On Wed, Mar 20, 2024 at 05:32:10AM +0000, Mathew, Cherry G.* wrote:
>> I look forward to your comments and test results, if any.
> I think moving heartbeat() to a callout context voids it's
> purpose.
Thank
Hello,
I'm responding to these queries together, as I they are both within the
GSoc context, and I just saw them in the archives now.
I assume you've read through Taylor's post here:
https://wiki.netbsd.org/projects/project/tickless/
Since he's listed as the mentor for this project, I'll leave i
Hello NetBSD,
I've been working a little bit on how to tackle tickless in the
kernel. I'll be hoping to send some preliminary patches later this month
or so - so this is mostly an email to co-ordinate with anyone else
working or aiming to work on similar things.
The only discernable change from a
> On Wed, 10 Apr 2024 12:37:31 +, Ice Cream
> said:
>> I've been working a little bit on how to tackle tickless in the
>> kernel. I'll be hoping to send some preliminary patches later this month
>> or so - so this is mostly an email to co-ordinate with anyone else
>> working or aimin
Hello Kernel people, et. al.,
I've been researching range querying over multi-dimensional keys,
(mainly related to its application in searching for ("delta","epsilon")
tuple timestamp range queries over a database of timers, events.)
This led me to the current key,value pair lookup code in the Ne
> On Wed, 9 Apr 2025 06:00:08 +, Emmanuel Dreyfus
> said:
[...]
> What is suprising is that it happens on a domU but not on another on
> the same dom0.
Is the dom0 MP ?
--
Math/(~cherry)
12 matches
Mail list logo
