Re: [RFC 00/32] State of MARS Reo-Redundancy Module

Typo correction: On 12/30/2016 11:57 PM, Thomas Schoebel-Theuer wrote: standalone servers with local hardware RAIDs. They are hosting about 500 MARS resources (originally DRBD resources) just for the web servers; This must read 2500. Somehow the leading "2" was eaten at wraparound.

Re: [RFC 00/32] State of MARS Reo-Redundancy Module

Typo correction: On 12/30/2016 11:57 PM, Thomas Schoebel-Theuer wrote: standalone servers with local hardware RAIDs. They are hosting about 500 MARS resources (originally DRBD resources) just for the web servers; This must read 2500. Somehow the leading "2" was eaten at wraparound.

[RFC 1/4] mm: remove unused TASK_SIZE_OF()

All users of TASK_SIZE_OF(tsk) have migrated to mm->task_size or TASK_SIZE_MAX since: commit d696ca016d57 ("x86/fsgsbase/64: Use TASK_SIZE_MAX for FSBASE/GSBASE upper limits"), commit a06db751c321 ("pagemap: check permissions and capabilities at open time"), Cc: Catalin Marinas

[RFC 1/4] mm: remove unused TASK_SIZE_OF()

All users of TASK_SIZE_OF(tsk) have migrated to mm->task_size or TASK_SIZE_MAX since: commit d696ca016d57 ("x86/fsgsbase/64: Use TASK_SIZE_MAX for FSBASE/GSBASE upper limits"), commit a06db751c321 ("pagemap: check permissions and capabilities at open time"), Cc: Catalin Marinas Cc: Will Deacon

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Fri, Dec 30 2016, Eric Anholt wrote: > OK, so the design is bad. When you said bug, I definitely thought you > were saying that the message shouldn't happen in the design. > > Given CMA's current design, should everyone using CMA see their logs > slowly growing with this message that is an

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Fri, Dec 30 2016, Eric Anholt wrote: > OK, so the design is bad. When you said bug, I definitely thought you > were saying that the message shouldn't happen in the design. > > Given CMA's current design, should everyone using CMA see their logs > slowly growing with this message that is an

[PATCH v2] perf/core: only check cpuctx with cgroup events during cgroup switch

v2: Fix build when no CONFIG_CGROUP_PERF Following conversation in CQM/CMT last series about speeding up the context switch for cgroup events: https://patchwork.kernel.org/patch/9478617/ This is a low-hanging fruit optimization. It replaces the iteration over the "pmus" list in cgroup switch by

[PATCH v2] perf/core: only check cpuctx with cgroup events during cgroup switch

v2: Fix build when no CONFIG_CGROUP_PERF Following conversation in CQM/CMT last series about speeding up the context switch for cgroup events: https://patchwork.kernel.org/patch/9478617/ This is a low-hanging fruit optimization. It replaces the iteration over the "pmus" list in cgroup switch by

Re: [PATCH] perf/core: only check cpuctx with cgroup events during cgroup switch

Hi David, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.10-rc1 next-20161224] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] perf/core: only check cpuctx with cgroup events during cgroup switch

Hi David, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.10-rc1 next-20161224] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] perf/core: only check cpuctx with cgroup events during cgroup switch

Hi David, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.10-rc1 next-20161224] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] perf/core: only check cpuctx with cgroup events during cgroup switch

Hi David, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.10-rc1 next-20161224] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] perf/core: only check cpuctx with cgroup events during cgroup switch

Following conversation in CQM/CMT last series about speeding up the context switch for cgroup events: https://patchwork.kernel.org/patch/9478617/ This is a low-hanging fruit optimization. It replaces the iteration over the "pmus" list in cgroup switch by an iteration over a new list that

[PATCH] perf/core: only check cpuctx with cgroup events during cgroup switch

Following conversation in CQM/CMT last series about speeding up the context switch for cgroup events: https://patchwork.kernel.org/patch/9478617/ This is a low-hanging fruit optimization. It replaces the iteration over the "pmus" list in cgroup switch by an iteration over a new list that

[RFC] memcpy_nocache() and memcpy_writethrough()

On Thu, Dec 29, 2016 at 08:56:13PM -0800, Dan Williams wrote: > > Um... Then we do have a problem - nocache variant of uaccess primitives > > does *not* guarantee that clwb is redundant. > > > > What about the requirements of e.g. tcp_sendmsg() with its use of > > skb_add_data_nocache()? What

[RFC] memcpy_nocache() and memcpy_writethrough()

On Thu, Dec 29, 2016 at 08:56:13PM -0800, Dan Williams wrote: > > Um... Then we do have a problem - nocache variant of uaccess primitives > > does *not* guarantee that clwb is redundant. > > > > What about the requirements of e.g. tcp_sendmsg() with its use of > > skb_add_data_nocache()? What

Re: [PATCH 1/2] x86/CPU: Add native CPUID variants returning a single datum

On Thu, Dec 29, 2016 at 1:30 AM, Borislav Petkov wrote: > On Wed, Dec 28, 2016 at 10:11:22AM -0800, Andy Lutomirski wrote: >> On a very quick read, it looks like none of your new call sites >> actually use the return value at all. Since you also appear to be >> consolidating them

Re: [PATCH 1/2] x86/CPU: Add native CPUID variants returning a single datum

On Thu, Dec 29, 2016 at 1:30 AM, Borislav Petkov wrote: > On Wed, Dec 28, 2016 at 10:11:22AM -0800, Andy Lutomirski wrote: >> On a very quick read, it looks like none of your new call sites >> actually use the return value at all. Since you also appear to be >> consolidating them all, would it

How should we handle variable address space sizes (Re: [RFC 3/4] x86/mm: define TASK_SIZE as current->mm->task_size)

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > Keep task's virtual address space size as mm_struct field which > exists for a long time - it's initialized in setup_new_exec() > depending on the new task's personality. > This way TASK_SIZE will always be the same

How should we handle variable address space sizes (Re: [RFC 3/4] x86/mm: define TASK_SIZE as current->mm->task_size)

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > Keep task's virtual address space size as mm_struct field which > exists for a long time - it's initialized in setup_new_exec() > depending on the new task's personality. > This way TASK_SIZE will always be the same as

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On Wed, Dec 28, 2016 at 6:53 PM, Carlos O'Donell wrote: > On 12/26/2016 09:24 PM, Kirill A. Shutemov wrote: >> On Mon, Dec 26, 2016 at 06:06:01PM -0800, Andy Lutomirski wrote: >>> On Mon, Dec 26, 2016 at 5:54 PM, Kirill A. Shutemov >>> wrote:

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On Wed, Dec 28, 2016 at 6:53 PM, Carlos O'Donell wrote: > On 12/26/2016 09:24 PM, Kirill A. Shutemov wrote: >> On Mon, Dec 26, 2016 at 06:06:01PM -0800, Andy Lutomirski wrote: >>> On Mon, Dec 26, 2016 at 5:54 PM, Kirill A. Shutemov >>> wrote: This patch introduces new rlimit resource to

Re: [v2 5/7] x86: Add emulation code for UMIP instructions

On Thu, Dec 29, 2016 at 9:23 PM, Ricardo Neri wrote: > On Tue, 2016-12-27 at 16:48 -0800, Andy Lutomirski wrote: >> >> >> > + if (nr_copied > 0) >> >> > + return -EFAULT; >> >> >> >> This should be the only EFAULT case.

Re: [v2 5/7] x86: Add emulation code for UMIP instructions

On Thu, Dec 29, 2016 at 9:23 PM, Ricardo Neri wrote: > On Tue, 2016-12-27 at 16:48 -0800, Andy Lutomirski wrote: >> >> >> > + if (nr_copied > 0) >> >> > + return -EFAULT; >> >> >> >> This should be the only EFAULT case. >> > Should this be EFAULT event if the

Re: [RFC 4/4] x86/arch_prctl: add ARCH_{GET,SET}_TASK_SIZE

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > Add arch_prctl getters/setters for size of virtual address space of task. > This adds ability to change task's virtual address space limit. > I need this for correctly restore virtual address space limits in CRIU. >

Re: [RFC 4/4] x86/arch_prctl: add ARCH_{GET,SET}_TASK_SIZE

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > Add arch_prctl getters/setters for size of virtual address space of task. > This adds ability to change task's virtual address space limit. > I need this for correctly restore virtual address space limits in CRIU. > Currently, on x86 there

Re: [RFC 2/4] x86/thread_info: kill TIF_ADDR32 in favour of ADDR_LIMIT_32BIT

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > This thread flag is completely x86-specific, consolidate it with > ADDR_LIMIT_32BIT personality which is defined but not used on x86. > It will free one of thread flags and consolidate personality with > other

Re: [RFC 2/4] x86/thread_info: kill TIF_ADDR32 in favour of ADDR_LIMIT_32BIT

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > This thread flag is completely x86-specific, consolidate it with > ADDR_LIMIT_32BIT personality which is defined but not used on x86. > It will free one of thread flags and consolidate personality with > other arches. > After this commit

Re: [RFC 1/4] mm: remove unused TASK_SIZE_OF()

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > All users of TASK_SIZE_OF(tsk) have migrated to mm->task_size or > TASK_SIZE_MAX since: > commit d696ca016d57 ("x86/fsgsbase/64: Use TASK_SIZE_MAX for > FSBASE/GSBASE upper limits"), > commit a06db751c321 ("pagemap:

Re: [RFC 1/4] mm: remove unused TASK_SIZE_OF()

On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov wrote: > All users of TASK_SIZE_OF(tsk) have migrated to mm->task_size or > TASK_SIZE_MAX since: > commit d696ca016d57 ("x86/fsgsbase/64: Use TASK_SIZE_MAX for > FSBASE/GSBASE upper limits"), > commit a06db751c321 ("pagemap: check permissions and

Re: [v2, 1/4] ARM: davinci: da8xx-dt: Add ti-aemif lookup for clock matching

On 08/10/2016 06:00 AM, Karl Beldan wrote: Many davinci boards (da830 and da850 families) don't have their clocks in DT yet and won't be successful in getting an unnamed aemif clock without explicitly registering them via clk_lookups, failing the ti-aemif memory driver probe. The current aemif

Re: [v2, 1/4] ARM: davinci: da8xx-dt: Add ti-aemif lookup for clock matching

On 08/10/2016 06:00 AM, Karl Beldan wrote: Many davinci boards (da830 and da850 families) don't have their clocks in DT yet and won't be successful in getting an unnamed aemif clock without explicitly registering them via clk_lookups, failing the ti-aemif memory driver probe. The current aemif

Re: [PATCH] This continues from this commit: 52f5684c8e1e ("kernel: use macros from compiler.h instead of __attribute__((...))")

On Sat, 2016-12-31 at 06:11 +0530, gidisr...@gmail.com wrote: > There is which provides macros for various gcc specific > constructs. Eg: __weak for __attribute__((weak)). I've cleaned all > instances of gcc specific attributes with the right macros for the crypto > subsystem. [] > diff --git

Re: [PATCH] This continues from this commit: 52f5684c8e1e ("kernel: use macros from compiler.h instead of __attribute__((...))")

On Sat, 2016-12-31 at 06:11 +0530, gidisr...@gmail.com wrote: > There is which provides macros for various gcc specific > constructs. Eg: __weak for __attribute__((weak)). I've cleaned all > instances of gcc specific attributes with the right macros for the crypto > subsystem. [] > diff --git

[PATCH] This continues from this commit: 52f5684c8e1e ("kernel: use macros from compiler.h instead of __attribute__((...))")

From: Gideon Israel Dsouza Very sorry about the previous broken patch. Here is an updated one. I submitted 4 total patches. They are part of task I've taken up to increase compiler portability in the kernel. I've cleaned up the subsystems under /kernel /mm /block and

[PATCH] This continues from this commit: 52f5684c8e1e ("kernel: use macros from compiler.h instead of __attribute__((...))")

From: Gideon Israel Dsouza Very sorry about the previous broken patch. Here is an updated one. I submitted 4 total patches. They are part of task I've taken up to increase compiler portability in the kernel. I've cleaned up the subsystems under /kernel /mm /block and /security, this patch

Re: [PATCH] crypto: Used macros from compiler.h instead of __attribute__(...))

Hi =, [auto build test ERROR on cryptodev/master] [also build test ERROR on v4.10-rc1 next-20161224] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] crypto: Used macros from compiler.h instead of __attribute__(...))

Hi =, [auto build test ERROR on cryptodev/master] [also build test ERROR on v4.10-rc1 next-20161224] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: PROBLEM: Kernel BUG with raid5 soft + Xen + DRBD - invalid opcode

Hello, Thanks for your reply. DRBD isn't part of the kernel ? I was thinking it has been included since 2.6.3x ? I've just tested without DRBD, the issue seems to remain. Can't see the "BUG", but the kernel crashed also. (A little bit later) I don't have full dump since I lost my network

Re: PROBLEM: Kernel BUG with raid5 soft + Xen + DRBD - invalid opcode

Hello, Thanks for your reply. DRBD isn't part of the kernel ? I was thinking it has been included since 2.6.3x ? I've just tested without DRBD, the issue seems to remain. Can't see the "BUG", but the kernel crashed also. (A little bit later) I don't have full dump since I lost my network

Geode LX AES/RNG driver triggers warning

Hi! I recently tested kernel v4.9 on my AMD Geode platform and noticed that its AES hardware driver triggers this warning on initialization: [1.265708] [ cut here ] [1.267932] WARNING: CPU: 0 PID: 1 at drivers/base/dd.c:344 driver_probe_device+0x5d/0x1ad [

Geode LX AES/RNG driver triggers warning

Hi! I recently tested kernel v4.9 on my AMD Geode platform and noticed that its AES hardware driver triggers this warning on initialization: [1.265708] [ cut here ] [1.267932] WARNING: CPU: 0 PID: 1 at drivers/base/dd.c:344 driver_probe_device+0x5d/0x1ad [

[PATCH] net: socket: don't set sk_uid to garbage value in ->setattr()

From: Eric Biggers ->setattr() was recently implemented for socket files to sync the socket inode's uid to the new 'sk_uid' member of struct sock. It does this by copying over the ia_uid member of struct iattr. However, ia_uid is actually only valid when ATTR_UID is set in

[PATCH] net: socket: don't set sk_uid to garbage value in ->setattr()

From: Eric Biggers ->setattr() was recently implemented for socket files to sync the socket inode's uid to the new 'sk_uid' member of struct sock. It does this by copying over the ia_uid member of struct iattr. However, ia_uid is actually only valid when ATTR_UID is set in ia_valid, indicating

[RFC 3/4] x86/mm: define TASK_SIZE as current->mm->task_size

Keep task's virtual address space size as mm_struct field which exists for a long time - it's initialized in setup_new_exec() depending on the new task's personality. This way TASK_SIZE will always be the same as current->mm->task_size. Previously, there could be an issue about different values of

[RFC 3/4] x86/mm: define TASK_SIZE as current->mm->task_size

Keep task's virtual address space size as mm_struct field which exists for a long time - it's initialized in setup_new_exec() depending on the new task's personality. This way TASK_SIZE will always be the same as current->mm->task_size. Previously, there could be an issue about different values of

[PATCH] crypto: Used macros from compiler.h instead of __attribute__(...))

From: = <=> This continues from this commit: 52f5684c8e1e ("kernel: use macros from compiler.h instead of __attribute__((...))") I submitted 4 total patches. They are part of task I've taken up to increase compiler portability in the kernel. I've cleaned up the subsystems under /kernel /mm

[PATCH] crypto: Used macros from compiler.h instead of __attribute__(...))

From: = <=> This continues from this commit: 52f5684c8e1e ("kernel: use macros from compiler.h instead of __attribute__((...))") I submitted 4 total patches. They are part of task I've taken up to increase compiler portability in the kernel. I've cleaned up the subsystems under /kernel /mm

[RFC 28/32] mars: add new module mars_proc

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/mars/mars_proc.c | 389 ++ drivers/staging/mars/mars/mars_proc.h | 34 +++ 2 files changed, 423 insertions(+) create mode 100644 drivers/staging/mars/mars/mars_proc.c create

[RFC 02/32] mars: add new module brick_say

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/brick_say.c | 920 +++ include/linux/brick/brick_say.h | 89 2 files changed, 1009 insertions(+) create mode 100644 drivers/staging/mars/brick_say.c create mode

[RFC 28/32] mars: add new module mars_proc

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/mars/mars_proc.c | 389 ++ drivers/staging/mars/mars/mars_proc.h | 34 +++ 2 files changed, 423 insertions(+) create mode 100644 drivers/staging/mars/mars/mars_proc.c create mode 100644

[RFC 02/32] mars: add new module brick_say

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/brick_say.c | 920 +++ include/linux/brick/brick_say.h | 89 2 files changed, 1009 insertions(+) create mode 100644 drivers/staging/mars/brick_say.c create mode 100644

[RFC 09/32] mars: add new module lib_rank

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lib/lib_rank.c | 87 +++ include/linux/brick/lib_rank.h | 136 2 files changed, 223 insertions(+) create mode 100644

[RFC 07/32] mars: add new module lib_pairing_heap

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/lib_pairing_heap.h | 109 + 1 file changed, 109 insertions(+) create mode 100644 include/linux/brick/lib_pairing_heap.h diff --git a/include/linux/brick/lib_pairing_heap.h

[RFC 06/32] mars: add new module brick

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/brick.c | 723 +++ include/linux/brick/brick.h | 620 + 2 files changed, 1343 insertions(+) create mode 100644

[RFC 09/32] mars: add new module lib_rank

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lib/lib_rank.c | 87 +++ include/linux/brick/lib_rank.h | 136 2 files changed, 223 insertions(+) create mode 100644 drivers/staging/mars/lib/lib_rank.c create mode

[RFC 07/32] mars: add new module lib_pairing_heap

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/lib_pairing_heap.h | 109 + 1 file changed, 109 insertions(+) create mode 100644 include/linux/brick/lib_pairing_heap.h diff --git a/include/linux/brick/lib_pairing_heap.h

[RFC 06/32] mars: add new module brick

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/brick.c | 723 +++ include/linux/brick/brick.h | 620 + 2 files changed, 1343 insertions(+) create mode 100644 drivers/staging/mars/brick.c create mode

[RFC 01/32] mars: add new module lamport

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lamport.c | 61 ++ include/linux/brick/lamport.h | 26 ++ 2 files changed, 87 insertions(+) create mode 100644 drivers/staging/mars/lamport.c create

[RFC 11/32] mars: add new module lib_timing

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lib/lib_timing.c | 68 + include/linux/brick/lib_timing.h | 182 ++ 2 files changed, 250 insertions(+) create mode 100644

[RFC 04/32] mars: add new module brick_checking

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/brick_checking.h | 107 +++ 1 file changed, 107 insertions(+) create mode 100644 include/linux/brick/brick_checking.h diff --git a/include/linux/brick/brick_checking.h

[RFC 01/32] mars: add new module lamport

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lamport.c | 61 ++ include/linux/brick/lamport.h | 26 ++ 2 files changed, 87 insertions(+) create mode 100644 drivers/staging/mars/lamport.c create mode 100644

[RFC 11/32] mars: add new module lib_timing

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lib/lib_timing.c | 68 + include/linux/brick/lib_timing.h | 182 ++ 2 files changed, 250 insertions(+) create mode 100644 drivers/staging/mars/lib/lib_timing.c create mode 100644

[RFC 04/32] mars: add new module brick_checking

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/brick_checking.h | 107 +++ 1 file changed, 107 insertions(+) create mode 100644 include/linux/brick/brick_checking.h diff --git a/include/linux/brick/brick_checking.h

[RFC 05/32] mars: add new module meta

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/meta.h | 106 + 1 file changed, 106 insertions(+) create mode 100644 include/linux/brick/meta.h diff --git a/include/linux/brick/meta.h

[RFC 00/32] State of MARS Reo-Redundancy Module

Hi together, here is my traditional annual status report on the development of MARS [1]. In the meantime, the out-of-tree MARS has replaced DRBD as the backbone of the 1&1 geo-redundancy feature as publicly advertised for 1&1 Shared Hosting Linux (ShaHoLin). MARS is also running on several other

[RFC 14/32] mars: add new module xio_net

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_net.c | 1849 + include/linux/xio/xio_net.h | 177 +++ 2 files changed, 2026 insertions(+) create mode 100644

[RFC 13/32] mars: add new module xio

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio.c | 227 include/linux/xio/xio.h | 319 ++ 2 files changed, 546 insertions(+) create mode 100644

[RFC 10/32] mars: add new module lib_limiter

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lib/lib_limiter.c | 163 + include/linux/brick/lib_limiter.h | 52 +++ 2 files changed, 215 insertions(+) create mode 100644

[RFC 08/32] mars: add new module lib_queue

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/lib_queue.h | 165 1 file changed, 165 insertions(+) create mode 100644 include/linux/brick/lib_queue.h diff --git a/include/linux/brick/lib_queue.h

[RFC 05/32] mars: add new module meta

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/meta.h | 106 + 1 file changed, 106 insertions(+) create mode 100644 include/linux/brick/meta.h diff --git a/include/linux/brick/meta.h b/include/linux/brick/meta.h new file mode 100644

[RFC 00/32] State of MARS Reo-Redundancy Module

Hi together, here is my traditional annual status report on the development of MARS [1]. In the meantime, the out-of-tree MARS has replaced DRBD as the backbone of the 1&1 geo-redundancy feature as publicly advertised for 1&1 Shared Hosting Linux (ShaHoLin). MARS is also running on several other

[RFC 14/32] mars: add new module xio_net

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_net.c | 1849 + include/linux/xio/xio_net.h | 177 +++ 2 files changed, 2026 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_net.c create mode 100644

[RFC 13/32] mars: add new module xio

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio.c | 227 include/linux/xio/xio.h | 319 ++ 2 files changed, 546 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio.c create

[RFC 10/32] mars: add new module lib_limiter

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/lib/lib_limiter.c | 163 + include/linux/brick/lib_limiter.h | 52 +++ 2 files changed, 215 insertions(+) create mode 100644 drivers/staging/mars/lib/lib_limiter.c create mode 100644

[RFC 08/32] mars: add new module lib_queue

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/lib_queue.h | 165 1 file changed, 165 insertions(+) create mode 100644 include/linux/brick/lib_queue.h diff --git a/include/linux/brick/lib_queue.h b/include/linux/brick/lib_queue.h new file

[RFC 19/32] mars: add new module xio_client

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_client.c | 1083 ++ include/linux/xio/xio_client.h | 105 +++ 2 files changed, 1188 insertions(+) create mode 100644

[RFC 03/32] mars: add new module brick_mem

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/brick_mem.c | 1080 ++ include/linux/brick/brick_mem.h | 218 2 files changed, 1298 insertions(+) create mode 100644 drivers/staging/mars/brick_mem.c create

[RFC 22/32] mars: add new module xio_trans_logger

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_trans_logger.c | 3410 include/linux/xio/xio_trans_logger.h | 271 ++ 2 files changed, 3681 insertions(+) create mode 100644

[RFC 19/32] mars: add new module xio_client

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_client.c | 1083 ++ include/linux/xio/xio_client.h | 105 +++ 2 files changed, 1188 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_client.c create mode

[RFC 03/32] mars: add new module brick_mem

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/brick_mem.c | 1080 ++ include/linux/brick/brick_mem.h | 218 2 files changed, 1298 insertions(+) create mode 100644 drivers/staging/mars/brick_mem.c create mode 100644

[RFC 22/32] mars: add new module xio_trans_logger

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_trans_logger.c | 3410 include/linux/xio/xio_trans_logger.h | 271 ++ 2 files changed, 3681 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_trans_logger.c

[RFC 18/32] mars: add new module xio_sio

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_sio.c | 578 ++ include/linux/xio/xio_sio.h | 68 2 files changed, 646 insertions(+) create mode 100644

[RFC 20/32] mars: add new module xio_if

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_if.c | 892 +++ include/linux/xio/xio_if.h | 109 2 files changed, 1001 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_if.c

[RFC 23/32] mars: add new module xio_server

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_server.c | 493 +++ include/linux/xio/xio_server.h | 91 + 2 files changed, 584 insertions(+) create mode 100644

[RFC 21/32] mars: add new module xio_copy

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_copy.c | 1005 include/linux/xio/xio_copy.h | 115 2 files changed, 1120 insertions(+) create mode 100644

[RFC 18/32] mars: add new module xio_sio

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_sio.c | 578 ++ include/linux/xio/xio_sio.h | 68 2 files changed, 646 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_sio.c create mode 100644

[RFC 20/32] mars: add new module xio_if

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_if.c | 892 +++ include/linux/xio/xio_if.h | 109 2 files changed, 1001 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_if.c create mode 100644

[RFC 23/32] mars: add new module xio_server

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_server.c | 493 +++ include/linux/xio/xio_server.h | 91 + 2 files changed, 584 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_server.c create mode

[RFC 21/32] mars: add new module xio_copy

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_copy.c | 1005 include/linux/xio/xio_copy.h | 115 2 files changed, 1120 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_copy.c create mode 100644

[RFC 31/32] mars: add new module Kconfig

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/Kconfig | 266 +++ 1 file changed, 266 insertions(+) create mode 100644 drivers/staging/mars/Kconfig diff --git a/drivers/staging/mars/Kconfig

[RFC 17/32] mars: add new module xio_bio

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_bio.c | 845 ++ include/linux/xio/xio_bio.h | 85 +++ 2 files changed, 930 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_bio.c

[RFC 31/32] mars: add new module Kconfig

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/Kconfig | 266 +++ 1 file changed, 266 insertions(+) create mode 100644 drivers/staging/mars/Kconfig diff --git a/drivers/staging/mars/Kconfig b/drivers/staging/mars/Kconfig new file mode

[RFC 17/32] mars: add new module xio_bio

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/xio_bio.c | 845 ++ include/linux/xio/xio_bio.h | 85 +++ 2 files changed, 930 insertions(+) create mode 100644 drivers/staging/mars/xio_bricks/xio_bio.c create mode 100644

[RFC 12/32] mars: add new module vfs_compat

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/vfs_compat.h | 48 1 file changed, 48 insertions(+) create mode 100644 include/linux/brick/vfs_compat.h diff --git a/include/linux/brick/vfs_compat.h

[RFC 26/32] mars: add new module net

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/mars/net.c | 109 1 file changed, 109 insertions(+) create mode 100644 drivers/staging/mars/mars/net.c diff --git a/drivers/staging/mars/mars/net.c

[RFC 12/32] mars: add new module vfs_compat

Signed-off-by: Thomas Schoebel-Theuer --- include/linux/brick/vfs_compat.h | 48 1 file changed, 48 insertions(+) create mode 100644 include/linux/brick/vfs_compat.h diff --git a/include/linux/brick/vfs_compat.h b/include/linux/brick/vfs_compat.h new

[RFC 26/32] mars: add new module net

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/mars/net.c | 109 1 file changed, 109 insertions(+) create mode 100644 drivers/staging/mars/mars/net.c diff --git a/drivers/staging/mars/mars/net.c b/drivers/staging/mars/mars/net.c new file

[RFC 30/32] mars: add new module Makefile

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/Makefile | 96 +++ 1 file changed, 96 insertions(+) create mode 100644 drivers/staging/mars/Makefile diff --git a/drivers/staging/mars/Makefile

[RFC 15/32] mars: add new module lib_mapfree

Signed-off-by: Thomas Schoebel-Theuer --- drivers/staging/mars/xio_bricks/lib_mapfree.c | 382 ++ include/linux/xio/lib_mapfree.h | 84 ++ 2 files changed, 466 insertions(+) create mode 100644

  1   2   3   4   5   6   7   >