linux-kernel - Re: [PATCH 12/19] OpenRISC: Scheduling/Process management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 19 Jun 2011 14:17:10 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	Jonas Bonn <jonas@...thpole.se>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 12/19] OpenRISC: Scheduling/Process management

Jonas Bonn <jonas@...thpole.se> writes:

> + * normally, the stack is found by doing something like p + THREAD_SIZE
> + * in or32, a page is 8192 bytes, which seems like a sane size
> + */
> +
> +#define THREAD_SIZE       PAGE_SIZE
> +#define THREAD_SIZE_ORDER 1

The ORDER == 1 and 8k you would get a 16k stack per thread,
which may be excessive?

> +#if 0
> +
> +/*
> + * The hlt_counter, disable_hlt and enable_hlt is just here as a hook
> if
You definitely don't need that.


-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/