All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andi Kleen <ak@suse.de>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: Source code compatibility in Stable series????
Date: Fri, 11 May 2001 12:21:59 MET-1	[thread overview]
Message-ID: <2983F527D00@vcnet.vc.cvut.cz> (raw)

On 11 May 01 at 12:03, Andi Kleen wrote:
> On Fri, May 11, 2001 at 02:56:35AM -0700, David S. Miller wrote:
> I guess it would be possible to add a HAVE_ZEROCOPY to skbuff.h to make
> it a bit easier for single source drivers.
> 
> --- include/linux/skbuff.h-o    Wed May  9 12:36:44 2001
> +++ include/linux/skbuff.h  Fri May 11 12:12:43 2001
> @@ -29,6 +29,7 @@
>  #define HAVE_ALLOC_SKB     /* For the drivers to know */
>  #define HAVE_ALIGNABLE_SKB /* Ditto 8)        */
>  #define SLAB_SKB       /* Slabified skbuffs       */
> +#define HAVE_ZEROCOPY      /* Zerocopy stack */ 

When I was updating VMware's vmnet, I decided to use

#ifdef skb_shinfo

This gives you maximal backward compatibility, as all public zerocopy
patches contain this macro. Only thing is that Dave has to remember
that when he turns skb_shinfo into inline function, an identity #define have
to be added.

Just my opinion - as you cannot add HAVE_ZEROCOPY to all already existing
and installed kernels.
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz



             reply	other threads:[~2001-05-11 10:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 12:21 Petr Vandrovec [this message]
2001-05-11 10:32 ` Source code compatibility in Stable series???? Andi Kleen
2001-05-11 10:39   ` Rogier Wolff
2001-05-11 10:44     ` Andi Kleen
2001-05-11 10:52       ` Rogier Wolff
2001-05-11 11:19       ` David S. Miller
2001-05-11 11:19     ` David S. Miller
2001-05-11 11:16 ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2001-05-11 13:08 Petr Vandrovec
2001-05-11  9:47 Rogier Wolff
2001-05-11  9:56 ` David S. Miller
2001-05-11 10:03   ` Andi Kleen
2001-05-11 11:13     ` David S. Miller

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=2983F527D00@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=ak@suse.de \
    --cc=davem@redhat.com \
    --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.