Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Geoffrey Espin <espin@idiom.com>
To: Pete Popov <ppopov@mvista.com>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: kmalloc/pci_alloc and skbuff's
Date: Wed, 19 Dec 2001 13:56:15 -0800	[thread overview]
Message-ID: <20011219135615.A3709@idiom.com> (raw)
In-Reply-To: <1008796988.31046.150.camel@zeus>; from Pete Popov on Wed, Dec 19, 2001 at 01:23:08PM -0800

> > Can one include one's own arch/mips/korva/skbuff.c?
> > But with network.o being a monolithic blob .o instead of a .a,

I figured someone might have some magic for hacking
arch/mips/Makefile ifdef CONFIG_NEC_KORVA (or any BSP/LSP).
I guess I'll have to make the effort.  :-)

> > Or will linux-mips.sf.net accept a patch for net/core/skbuff.c?
> Up the the maintainer, but it's really not the right fix so I think it's
> best for you or your customer to keep that patch locally.

I talked Jun into checking in the Markham patches... but will
have to add a comment to the pci_xxx files that one has to get
a separate patch for net/core/skbuff.c if using PCI with a generic
driver.

> Another approach would be for you to preallocate your network buffers in
> your driver, attach them permanently to the rx/tx descriptors, and then

The idea was not to mess with any PCI drivers. 2.5 is not an option for me.

Thanks, Pete.

Geoff
-- 
Geoffrey Espin espin@idiom.com

  reply	other threads:[~2001-12-19 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 20:38 kmalloc/pci_alloc and skbuff's Geoffrey Espin
2001-12-19  9:05 ` Gleb O. Raiko
2001-12-19 17:09   ` James Simmons
2001-12-19 18:56     ` Geoffrey Espin
2001-12-19 19:12       ` Pete Popov
2001-12-19 19:53         ` Geoffrey Espin
2001-12-19 21:23           ` Pete Popov
2001-12-19 21:56             ` Geoffrey Espin [this message]
2001-12-19 22:06               ` Pete Popov

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=20011219135615.A3709@idiom.com \
    --to=espin@idiom.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ppopov@mvista.com \
    /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