From: Parag Nemade <cranium2003@yahoo.com>
To: kernerl mail <linux-kernel@vger.kernel.org>
Subject: Basic understanding about sk_buff packet handling
Date: Wed, 14 Apr 2004 08:26:43 -0700 (PDT) [thread overview]
Message-ID: <20040414152643.62896.qmail@web41414.mail.yahoo.com> (raw)
hello,
As a part of my kernel project i come to
some problems regarding sk_buff structure
1) i want to add two fields of each 4 bytes in sk_buff
structure what is the effect of it on kernel packet
processing? Is there any -ve effect?
2) if i am going to increase it by 8 bytes then what
will happen to net packet size and its data part? Is
that all will fit in sk_buff?
3) Which is best to include my 2 fields in sk_buff or
include its total value at end of data part?
4) When kernel passes the packet to dest host all
sk_buff fields are also transferred or only packet
header and data?
parag.
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html
reply other threads:[~2004-04-14 15:28 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=20040414152643.62896.qmail@web41414.mail.yahoo.com \
--to=cranium2003@yahoo.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®