From: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
To: <wg@grandegger.com>, <mkl@pengutronix.de>, <davem@davemloft.net>
Cc: <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Subject: [PATCH] net: can: Increase tx queue length
Date: Sat, 9 Mar 2019 19:37:26 +0530 [thread overview]
Message-ID: <1552140446-31535-1-git-send-email-appana.durga.rao@xilinx.com> (raw)
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.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.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;
--
2.7.4
next reply other threads:[~2019-03-09 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 14:07 Appana Durga Kedareswara rao [this message]
2019-03-09 14:22 ` Andre Naujoks
2019-03-09 14:40 ` Appana Durga Kedareswara Rao
2019-03-09 14:56 ` Andre Naujoks
2019-03-09 15:50 ` Toke Høiland-Jørgensen
2019-03-10 5:07 ` Dave Taht
2019-03-10 17:30 ` Oliver Hartkopp
2019-03-15 10:04 ` Appana Durga Kedareswara Rao
2019-03-15 13:53 ` Oliver Hartkopp
2019-03-10 13:36 ` Martin Jerabek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1552140446-31535-1-git-send-email-appana.durga.rao@xilinx.com \
--to=appana.durga.rao@xilinx.com \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®