On Fri, Nov 07, 2014 at 04:41:55PM +0900, Kengo NAKAHARA wrote:
Could you comment the specification and implementation?
The user should not be on the hook to set processor affinity for the
interrupts. That is more properly the responsibility of the designer
and OS.
Dave
--
David Young
Hi,
(2014/11/13 11:54), David Young wrote:
On Fri, Nov 07, 2014 at 04:41:55PM +0900, Kengo NAKAHARA wrote:
Could you comment the specification and implementation?
The user should not be on the hook to set processor affinity for the
interrupts. That is more properly the responsibility of the
Hi,
I'm back to the work.
Here is a new patch: http://www.netbsd.org/~ozaki-r/psz-ifnet.diff
I think the patch reflects rmind's suggestions:
- Use pserialize for IFNET_FOREACH
- but use a lock for blockable/sleepable critical sections
- cpu_intr_p workaround for HW interrupt
Any comments?
Date: Thu, 13 Nov 2014 12:43:26 +0900
From: Ryota Ozaki ozak...@netbsd.org
Here is a new patch: http://www.netbsd.org/~ozaki-r/psz-ifnet.diff
I think the patch reflects rmind's suggestions:
- Use pserialize for IFNET_FOREACH
- but use a lock for blockable/sleepable critical
On Wed, Nov 12, 2014 at 2:53 AM, Taylor R Campbell campb...@mumble.net wrote:
Date: Tue, 11 Nov 2014 17:42:51 +
From: Antti Kantee po...@iki.fi
2: init_main ordering
I think that code reading is an absolute requirement there, i.e. we
should be able to know offline
(snip)
How about spending your energy to investigate real dependencies, for example:
http://nxr.netbsd.org/xref/src/sys/kern/init_main.c#559
Does pax depend on veriexec?
Does ipsec depend on pax?
On Thu, Nov 13, 2014 at 1:26 PM, Taylor R Campbell
campbell+netbsd-tech-k...@mumble.net wrote:
Date: Thu, 13 Nov 2014 12:43:26 +0900
From: Ryota Ozaki ozak...@netbsd.org
Here is a new patch: http://www.netbsd.org/~ozaki-r/psz-ifnet.diff
I think the patch reflects rmind's
