From: danielhilst@gmail.com (Daniel.)
To: kernelnewbies@lists.kernelnewbies.org
Subject: ndo_start_xmit what to return when packet is too big!?
Date: Tue, 20 Sep 2016 00:06:26 -0300 [thread overview]
Message-ID: <CAF3SDA7Nixvb2b256nLJdC6AW9hhHt4du2aS1JPzmDirZbRshQ@mail.gmail.com> (raw)
Hi everybody,
I was looking at network chapter of LDD3. The .ndo_start_xmit member
of struct net_device_ops should return netdev_tx_t which are:
enum netdev_tx {
__NETDEV_TX_MIN = INT_MIN, /* make sure enum is signed */
NETDEV_TX_OK = 0x00, /* driver took care of packet */
NETDEV_TX_BUSY = 0x10, /* driver tx path was busy*/
NETDEV_TX_LOCKED = 0x20, /* driver tx lock was already taken */
};
I'm deling with some awkward hardware where the MTU is only 32 bytes
and was wondering. What should that function return in case of "too
large packet"?!?!?
Best regards,
--
"Do or do not. There is no try"
Yoda Master
reply other threads:[~2016-09-20 3:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAF3SDA7Nixvb2b256nLJdC6AW9hhHt4du2aS1JPzmDirZbRshQ@mail.gmail.com \
--to=danielhilst@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).