From: "David S. Miller" <davem@redhat.com>
To: Tommy Christensen <tommy.christensen@tpack.net>
Cc: greearb@candelatech.com, netdev@oss.sgi.com
Subject: Re: [PATCH] Handle shared SKBs in VLAN receive code
Date: Mon, 13 Oct 2003 10:19:35 -0700 [thread overview]
Message-ID: <20031013101935.231fb1fd.davem@redhat.com> (raw)
In-Reply-To: <3F892629.7090206@tpack.net>
On Sun, 12 Oct 2003 12:00:09 +0200
Tommy Christensen <tommy.christensen@tpack.net> wrote:
> Bear with me, but this is how I understand it:
>
> - The sk_buff *structure* is read-only on a shared SKB.
> skb_share_check(skb) breaks the sharing, thus allowing
> updates of skb->dev, skb->len etc.
> But the SKB still points at the same data buffer.
>
> - The *data* buffer is read-only on a cloned SKB.
> skb_cow() or skb_copy() or ... gives us a writeable buffer.
skb_copy() makes both the struct sk_buff and the data it points
to unique and yours alone to modify however you wish.
prev parent reply other threads:[~2003-10-13 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 23:38 [PATCH] Handle shared SKBs in VLAN receive code Tommy Christensen
2003-10-10 23:52 ` Ben Greear
2003-10-11 0:09 ` Tommy Christensen
2003-10-11 19:03 ` Ben Greear
2003-10-11 19:03 ` David S. Miller
2003-10-11 19:55 ` Ben Greear
2003-10-11 19:54 ` David S. Miller
2003-10-12 10:00 ` Tommy Christensen
2003-10-13 17:19 ` David S. Miller [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=20031013101935.231fb1fd.davem@redhat.com \
--to=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=tommy.christensen@tpack.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.