That?s great. Thanks!
- Helin
From: Vijayakumar Muthuvel Manickam [mailto:mmvi...@gmail.com]
Sent: Monday, June 15, 2015 9:11 AM
To: Zhang, Helin
Cc: thomas.monjalon at 6wind.com; dev at dpdk.org
Subject: Re: [dpdk-dev] [PATCH] kni: Add link status update
Hi Helin,
Since Stepthen
Any response for my comments? Did I miss anything?
- Helin
> -Original Message-
> From: Zhang, Helin
> Sent: Tuesday, May 19, 2015 8:54 AM
> To: Vijayakumar Muthuvel Manickam; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] kni: Add link status update
>
> Hello
kam; dev at dpdk.org
> > Subject: RE: [dpdk-dev] [PATCH] kni: Add link status update
> >
> > Hello
> >
> > > -Original Message-
> > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Vijayakumar
> > > Muthuvel Manickam
> > >
Hello
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Vijayakumar
> Muthuvel Manickam
> Sent: Tuesday, May 19, 2015 7:33 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] kni: Add link status update
>
> Add an ioctl command in
I agree that this looks like a good facility to have but this is not
the right way to do it.
There are already several facilities to accomplish the same thing.
1. You can use the operstate functionality in kernel to manipulate carrier
from another application (read Documentation/operstate.txt)
Add an ioctl command in rte_kni module to enable
DPDK applications to propagate link state changes to
kni virtual interfaces.
Signed-off-by: Vijayakumar Muthuvel Manickam
---
.../linuxapp/eal/include/exec-env/rte_kni_common.h | 2 ++
lib/librte_eal/linuxapp/kni/kni_misc.c | 39 +
6 matches
Mail list logo
