From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paarvai Naai Subject: Re: Fwd: Querying current tx_queue usage of a SocketCAN interface Date: Fri, 3 Apr 2015 13:53:17 -0700 Message-ID: References: <55187FF1.7020701@optusnet.com.au> <5519E5A9.7080104@optusnet.com.au> <551A0FF3.4070400@optusnet.com.au> <551C7D79.50906@optusnet.com.au> <551CE5C9.6020600@pengutronix.de> <551DEE7C.6040202@optusnet.com.au> <1f3de4fb-6a20-48aa-9b6b-102ef079e299@email.android.com> <7573caff-e3ce-4927-a12b-11d98b8cb333@email.android.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-ob0-f171.google.com ([209.85.214.171]:34851 "EHLO mail-ob0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752349AbbDCUxS (ORCPT ); Fri, 3 Apr 2015 16:53:18 -0400 Received: by obbfy7 with SMTP id fy7so99356177obb.2 for ; Fri, 03 Apr 2015 13:53:17 -0700 (PDT) In-Reply-To: <7573caff-e3ce-4927-a12b-11d98b8cb333@email.android.com> Sender: linux-can-owner@vger.kernel.org List-ID: To: Marc Kleine-Budde Cc: Tom Evans , Dan Egnor , linux-can@vger.kernel.org Hi Marc, > Just glancing at libsocketcan, I don't see an option to set the tx queue len. The parameter is not CAN specific. You are right, of course. My confusion stemmed from the fact that someone else here pulled down libsocketcan and then modified it to add this as an API call to libsocketcan.{h,cc}. Thanks for setting me straight. I will look into this further. Paarvai