From: Ben Greear <greearb@candelatech.com>
To: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: return values for hard_start_xmit and dev_queue_xmit
Date: Wed, 13 Oct 2004 11:53:37 -0700 [thread overview]
Message-ID: <416D79B1.1090707@candelatech.com> (raw)
In-Reply-To: <416D7526.8050206@candelatech.com>
Ben Greear wrote:
> The dev_queue_xmit method is fairly well documented in dev.c, but
> there are zero comments in the netdevice.h file to explain what the
> acceptable return values for hard_start_xmit are.
Actually, looks like I'm wrong here. The comments in dev.c say that
error codes are < 0, but in fact, this can easily return NET_XMIT_DROP
which is a positive value (1).
Maybe the truth is that any non-zero return value from dev_queue_xmit
is an error?
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2004-10-13 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 18:34 return values for hard_start_xmit and dev_queue_xmit Ben Greear
2004-10-13 18:53 ` Ben Greear [this message]
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=416D79B1.1090707@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).