[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY4PR02MB2183E0667CF67DEE6A297FF8DC4E0@CY4PR02MB2183.namprd02.prod.outlook.com>
Date: Sat, 9 Mar 2019 14:40:32 +0000
From: Appana Durga Kedareswara Rao <appanad@...inx.com>
To: Andre Naujoks <nautsch2@...il.com>,
"wg@...ndegger.com" <wg@...ndegger.com>,
"mkl@...gutronix.de" <mkl@...gutronix.de>,
"davem@...emloft.net" <davem@...emloft.net>
CC: "linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] net: can: Increase tx queue length
Hi Andre,
<Snip>
>
> On 3/9/19 3:07 PM, Appana Durga Kedareswara rao wrote:
> > While stress testing the CAN interface on xilinx axi can in loopback
> > mode getting message "write: no buffer space available"
> > Increasing device tx queue length resolved the above mentioned issue.
>
> No need to patch the kernel:
>
> $ ip link set <dev-name> txqueuelen 500
>
> does the same thing.
Thanks for the review...
Agree but it is not an out of box solution right??
Do you have any idea for socket can devices why the tx queue length is 10 whereas
for other network devices (ex: ethernet) it is 1000 ??
Regards,
Kedar.
>
> >
> > Signed-off-by: Appana Durga Kedareswara rao
> > <appana.durga.rao@...inx.com>
> > ---
> > --> Network devices default tx_queue_len is 1000 but for socket
> > can device it is 10 any reason for it??
> >
> > drivers/net/can/dev.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/can/dev.c b/drivers/net/can/dev.c index
> > c05e4d5..32bd5be 100644
> > --- a/drivers/net/can/dev.c
> > +++ b/drivers/net/can/dev.c
> > @@ -642,7 +642,7 @@ static void can_setup(struct net_device *dev)
> > dev->mtu = CAN_MTU;
> > dev->hard_header_len = 0;
> > dev->addr_len = 0;
> > - dev->tx_queue_len = 10;
> > + dev->tx_queue_len = 500;
> >
> > /* New-style flags. */
> > dev->flags = IFF_NOARP;
> >
Powered by blists - more mailing lists