From: Prasanna P Subash <psubash@turbolinux.com>
To: "Dragos, Radu" <dragosr@eeng.dcu.ie>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Documentation about programming sk_buffers
Date: Wed, 21 Feb 2001 16:45:16 -0800 [thread overview]
Message-ID: <20010221164516.B671@turbolinux.com> (raw)
In-Reply-To: <025a01c09c11$ed83f880$b323ce88@eeng.dcu.ie>
In-Reply-To: <025a01c09c11$ed83f880$b323ce88@eeng.dcu.ie>; from Dragos, Radu on Wed, Feb 21, 2001 at 02:23:53PM -0000
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
maybe this will be useful.
http://www.linux-sna.org/events/papers/Bang%21inux-netstack-2001/skb%20definition.html
On Wed, Feb 21, 2001 at 02:23:53PM -0000, Dragos, Radu wrote:
> Does anyone know some good documentation about handling sk_buffers ?
>
> I'll need to work with them for some kind of filter.
>
> Thanks.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Prasanna Subash --- psubash@turbolinux.com --- TurboLinux, INC
------------------------------------------------------------------------
Linux, the choice | There are three things men can do with
of a GNU generation -o) | women: love them, suffer for them, or turn
Kernel 2.4.0-ac4 /\\ | them into literature. -- Stephen Stills
on a i686 _\\_v |
|
------------------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-02-22 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 14:23 Documentation about programming sk_buffers Dragos, Radu
2001-02-22 0:45 ` Prasanna P Subash [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=20010221164516.B671@turbolinux.com \
--to=psubash@turbolinux.com \
--cc=dragosr@eeng.dcu.ie \
--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