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]
Message-ID: <1287152769.29097.1519.camel@twins>
Date:	Fri, 15 Oct 2010 16:26:09 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Venkatesh Pallipadi <venki@...gle.com>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-kernel@...r.kernel.org, Paul Turner <pjt@...gle.com>,
	Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [PATCH 3/8] Add a PF flag for ksoftirqd identification

On Mon, 2010-10-04 at 17:03 -0700, Venkatesh Pallipadi wrote:
> @@ -1234,6 +1234,7 @@ struct task_struct {
>  
>         /* Revert to default priority/policy when forking */
>         unsigned sched_reset_on_fork:1;
> +       unsigned sched_thread_bound:1;  /* Thread bound to specific cpu */
>  
>         pid_t pid;
>         pid_t tgid;
> @@ -1708,7 +1709,7 @@ extern void thread_group_times(struct task_struct *p, cputime_t *ut, cputime_t *
>  #define PF_SWAPWRITE   0x00800000      /* Allowed to write to swap */
>  #define PF_SPREAD_PAGE 0x01000000      /* Spread page cache over cpuset */
>  #define PF_SPREAD_SLAB 0x02000000      /* Spread some slab caches over cpuset */
> -#define PF_THREAD_BOUND        0x04000000      /* Thread bound to specific cpu */
> +#define PF_KSOFTIRQD   0x04000000      /* I am ksoftirqd */ 

No need to do that, there's two free bits, 0x1 and 0x1000 (although this
latter is pending in Andrew's tree).
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ