mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Jianyong Zhang <jzhang@cse.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a problem about non-linear sk_buff
Date: Thu, 11 Oct 2001 13:42:08 +0400	[thread overview]
Message-ID: <20011011134208.31535158.johnpol@2ka.mipt.ru> (raw)
In-Reply-To: <Pine.SOL.4.33.0110092342190.24061-100000@frack.cse.psu.edu>
In-Reply-To: <Pine.SOL.4.33.0110092342190.24061-100000@frack.cse.psu.edu>

On Tue, 9 Oct 2001 23:51:17 -0400 (EDT)
Jianyong Zhang <jzhang@cse.psu.edu> wrote:

JZ> Hi,

JZ> I'm a newcomer of this list.  I want to understand the tcp/ip stack's
JZ> implementaion, and hope that I can get your help.

kernlel-net is also good for this kind of questions.

JZ> I find that that sk_buff can be fragmented, and it's called nonlinear.
JZ> What's the meaning of nonlinear?  And what are the meaning of
sk_buff's

May be because of MTU?

JZ> fields: skb->data_len and skb_shinfo(skb)?  I have no idea about them.

As I've right understood it from 
www.linux.org.uk/Documents/buffers.html (excellent Alan's book)
http://kernelnewbies.org/documents/ipnetworking/linuxipnetworking.html
(the best source of documentation fobeginners)
and skbuff.h
skb->data_len is actuall length of the data( that is all packet length -
header length).

skb_shinfo(skb) returns structure that containig number of fragments, list
of it, and some other( what? ).

JZ> May you explain them?  Thank you.

I'm trying, but it can be absolutelly wrong :)

JZ> Jianyong Zhang

Evgeniy Polyakov.
---
WBR. //s0mbre

      parent reply	other threads:[~2001-10-11  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10  3:51 Jianyong Zhang
2001-10-11  2:08 ` Evgeniy Polyakov
2001-10-11  9:42 ` Evgeniy Polyakov [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=20011011134208.31535158.johnpol@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=jzhang@cse.psu.edu \
    --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®