On Mon, Nov 15, 2010 at 05:40:05PM +0100, Johnny Billquist wrote:
> [...] but rwlocks can not be fixed without more work. :-(
I wouldn't be particularly surprised if replacing the current overbred
rwlock code with a simple implementation using a single mutex and
condvar made it go faster... or at
On Mon, Nov 15, 2010 at 03:47:32PM -0500, der Mouse wrote:
> > [...] just forward declarations of the structs.
>
> > (this is, btw, one of the reasons to avoid silly typedefs)
>
> I'm not sure what typedefs have to do with it. typedeffing a name to
> an incomplete ("forward") struct type w
On Mon, Nov 15, 2010 at 10:41:55PM +, David Laight wrote:
> > Indeed. Properly speaking though, headers that are exported to
> > userland should define only the precise symbols that userland needs;
> > kernel-only material should be kept elsewhere.
>
> One start would be to add a sys/proc
On Mon, Nov 15, 2010 at 08:34:40PM +, David Holland wrote:
> (moving this to tech-kern because it's the right place and per request)
>
> On Mon, Nov 15, 2010 at 11:24:21AM +0900, Masao Uebayashi wrote:
> > > Every header file should include the things it requires to compile.
> > > Therefore,
>> I've long felt this way: that, except for a very few examples like
>> that are defined to depend on context, the order of
>> #includes should not matter. In particular, if multiple files must
>> be included, any of them may come first - so any file that generates
>> errors if it's included fir
On Mon, Nov 15, 2010 at 03:47:32PM -0500, der Mouse wrote:
> >>> Every header file should include the things it requires to compile.
>
> I've long felt this way: that, except for a very few examples like
> that are defined to depend on context, the order of
> #includes should not matter. In part
>>> Every header file should include the things it requires to compile.
I've long felt this way: that, except for a very few examples like
that are defined to depend on context, the order of
#includes should not matter. In particular, if multiple files must be
included, any of them may come firs
(moving this to tech-kern because it's the right place and per request)
On Mon, Nov 15, 2010 at 11:24:21AM +0900, Masao Uebayashi wrote:
> > Every header file should include the things it requires to compile.
> > Therefore, there should in principle be no cases where a header file
> > (or sourc
On 11/13/10 11:16, Anders Magnusson wrote:
(a little side-note, but may be interesting)
On 11/13/2010 04:17 AM, Matt Thomas wrote:
Eventually, most operations come down to compare and swap. It's just too
damn useful to not have as a primitive. Even if some of the platforms
have to emulate it so
On 11/15/10 14:55, Johnny Billquist wrote:
On 11/14/10 20:16, David Holland wrote:
On Sat, Nov 13, 2010 at 01:45:40AM +0900, Izumi Tsutsui wrote:
> > Wow. I guess you can add me to the list of people leaving.
>
> There is no perfect world and we don't have enough resources.
>
> Any help to keep
On 11/14/10 20:16, David Holland wrote:
On Sat, Nov 13, 2010 at 01:45:40AM +0900, Izumi Tsutsui wrote:
> > Wow. I guess you can add me to the list of people leaving.
>
> There is no perfect world and we don't have enough resources.
>
> Any help to keep support for ancient machines a
11 matches
Mail list logo
