All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Andi Kleen <ak@suse.de>
Cc: "Jens Hoffrichter" <HOFFRICH@de.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: Allocation of sk_buffs in the kernel
Date: Thu, 23 Aug 2001 00:42:45 -0300	[thread overview]
Message-ID: <20010823004245.O5062@conectiva.com.br> (raw)
In-Reply-To: <OF55D2E221.5E62CB41-ONC1256AB0.0052D2D3@de.ibm.com.suse.lists.linux.kernel> <oupd75no4b3.fsf@pigdrop.muc.suse.de>
In-Reply-To: <oupd75no4b3.fsf@pigdrop.muc.suse.de>; from ak@suse.de on Thu, Aug 23, 2001 at 05:14:56AM +0200

Em Thu, Aug 23, 2001 at 05:14:56AM +0200, Andi Kleen escreveu:
> [1] There may be a few unnormal ones that do; e.g. vendor driver
> writers seem to frequently try to reuse skbuffs privately because they're
> used to that from other OS. It is discouraged and somewhat tricky, but
> possible.

The original 802.2 stack from procom, used frame_t all over the core stack,
with only the entry/exit points manipulating skb's. On entry from the core
networking stack and from upper protocols (NetBEUI in procom case) they
allocated a frame_t from a pool and initialited pointers to the mac and llc
headers and stored the skb type in another frame_t member, pointing to the
skb memory and used those pointers instead of skb->h and skb->nh.  That
way, I think, they could use the core for several OSes.

Maybe Jens should use something like WAITQUEUE_DEBUG if he want to know
where alloc_skb and friends were called, see include/linux/wait.h 8)

- Arnaldo


  reply	other threads:[~2001-08-23  3:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF55D2E221.5E62CB41-ONC1256AB0.0052D2D3@de.ibm.com.suse.lists.linux.kernel>
2001-08-23  3:14 ` Allocation of sk_buffs in the kernel Andi Kleen
2001-08-23  3:42   ` Arnaldo Carvalho de Melo [this message]
2001-08-23  9:29 Jens Hoffrichter
2001-08-23  9:46 ` Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2001-08-23  9:07 Jens Hoffrichter
2001-08-23  9:01 Jens Hoffrichter
2001-08-23  9:12 ` Arnaldo Carvalho de Melo
2001-08-22 15:10 Jens Hoffrichter

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=20010823004245.O5062@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=HOFFRICH@de.ibm.com \
    --cc=ak@suse.de \
    --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 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.