public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Bendi Vinaya Kumar <vbendi@cs.clemson.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Skbuff Trimming
Date: 28 Jun 2002 05:04:26 +0200	[thread overview]
Message-ID: <p73k7okm7d1.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Bendi Vinaya Kumar's message of "28 Jun 2002 00:16:41 +0200"

Bendi Vinaya Kumar <vbendi@cs.clemson.edu> writes:

> But, it does not do the same on
> "frag_list". Why?

frag_list is not a general purpose skbuff facility and is not used by
most protocols and not directly supported by most of skbuff.c It is just 
supported by some specific paths to enable lazy defragmenting. It is not
an attempt to turn skbuffs into mbufs.

-Andi


       reply	other threads:[~2002-06-28  3:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.44.0206271756540.727-100000@noisy.cs.clemson.edu.suse.lists.linux.kernel>
2002-06-28  3:04 ` Andi Kleen [this message]
2002-06-28 19:06   ` Skbuff Trimming Bendi Vinaya Kumar
2002-06-30  2:14   ` Bendi Vinaya Kumar
2002-06-27 22:10 Bendi Vinaya Kumar

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=p73k7okm7d1.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vbendi@cs.clemson.edu \
    /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