On Sun, 16 Apr 2017, Jason A. Donenfeld wrote:
> I rather like this option of padata, which, since it lives in
> kernel/padata.c and linux/padata.h, should be generic and useful for
> other components. Seems like the ability to allocate it for a
> particular set of worker CPUs and callback CPUs
On Sun, 16 Apr 2017, Jason A. Donenfeld wrote:
> I rather like this option of padata, which, since it lives in
> kernel/padata.c and linux/padata.h, should be generic and useful for
> other components. Seems like the ability to allocate it for a
> particular set of worker CPUs and callback CPUs
I rather like this option of padata, which, since it lives in
kernel/padata.c and linux/padata.h, should be generic and useful for
other components. Seems like the ability to allocate it for a
particular set of worker CPUs and callback CPUs could be useful down
the line. Would rather not see it
I rather like this option of padata, which, since it lives in
kernel/padata.c and linux/padata.h, should be generic and useful for
other components. Seems like the ability to allocate it for a
particular set of worker CPUs and callback CPUs could be useful down
the line. Would rather not see it
No users outside of padata.c
Signed-off-by: Thomas Gleixner
Cc: Steffen Klassert
Cc: linux-cry...@vger.kernel.org
---
include/linux/padata.h |3 ---
kernel/padata.c| 34 +-
2 files changed, 17
No users outside of padata.c
Signed-off-by: Thomas Gleixner
Cc: Steffen Klassert
Cc: linux-cry...@vger.kernel.org
---
include/linux/padata.h |3 ---
kernel/padata.c| 34 +-
2 files changed, 17 insertions(+), 20 deletions(-)
---
6 matches
Mail list logo