On Tue, 2015-07-07 at 15:57 +0200, Ursula Braun wrote:
> Eric,
>
> understood, would it be acceptable if the SMC-specific hooks in the
> TCP-code are enclosed with "#ifdef CONFIG_SMC ... #endif"?
If this CONFIG_SMC is enabled only on relevant builds, I guess it would
be ok. (Try to use helpers in
Eric,
understood, would it be acceptable if the SMC-specific hooks in the
TCP-code are enclosed with "#ifdef CONFIG_SMC ... #endif"?
Regards, Ursula
On Mon, 2015-07-06 at 18:08 +0200, Eric Dumazet wrote:
> On Mon, 2015-07-06 at 17:11 +0200, Ursula Braun wrote:
> > From: Ursula Braun
> >
> > Th
On Mon, 2015-07-06 at 17:11 +0200, Ursula Braun wrote:
> From: Ursula Braun
>
> The SMC-R protocol defines dynamic discovery of peers. This is done by
> implementing experimental TCP options as defined in RFC6994. The TCP code
> needs to be extended to support RFC6994.
>
> Setting the TCP experi
From: Ursula Braun
The SMC-R protocol defines dynamic discovery of peers. This is done by
implementing experimental TCP options as defined in RFC6994. The TCP code
needs to be extended to support RFC6994.
Setting the TCP experimental option for SMC-R [2] will be triggered from
kernel exploiters
