r ;
> sta...@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4] net/tap: fix device removal when no queues
> exist
>
>
>
> > On May 22, 2018, at 11:50 PM, Varghese, Vipin
> wrote:
> >
> > Hi Ophir,
> >
> > One suggestion shared inline to email
> >
> On May 22, 2018, at 11:50 PM, Varghese, Vipin
> wrote:
>
> Hi Ophir,
>
> One suggestion shared inline to email
>
>
>
>>
>> diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
>> index
>> c006d07..52ef799 100644
>> --- a/drivers/net/tap/rte_eth_tap.c
>> +++ b/driv
Hi Ophir,
One suggestion shared inline to email
>
> diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
> index
> c006d07..52ef799 100644
> --- a/drivers/net/tap/rte_eth_tap.c
> +++ b/drivers/net/tap/rte_eth_tap.c
> @@ -929,6 +929,15 @@ tap_dev_close(struct rte_eth_dev
> On May 21, 2018, at 2:54 AM, Ophir Munk wrote:
>
> TAP device is created following its first queue creation. Multiple
> queues can be added or removed over time. In Linux terminology those
> are file descriptors which are opened or closed over time. As long as
> the number of opened file desc
TAP device is created following its first queue creation. Multiple
queues can be added or removed over time. In Linux terminology those
are file descriptors which are opened or closed over time. As long as
the number of opened file descriptors is positive - TAP device will
appear as a Linux device.
5 matches
Mail list logo
