From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: Source code compatibility in Stable series????
Date: Fri, 11 May 2001 12:03:41 +0200 [thread overview]
Message-ID: <20010511120341.A5112@gruyere.muc.suse.de> (raw)
In-Reply-To: <200105110947.LAA18167@cave.bitwizard.nl> <15099.46931.914571.475632@pizda.ninka.net>
In-Reply-To: <15099.46931.914571.475632@pizda.ninka.net>; from davem@redhat.com on Fri, May 11, 2001 at 02:56:35AM -0700
On Fri, May 11, 2001 at 02:56:35AM -0700, David S. Miller wrote:
>
> Rogier Wolff writes:
> > It seems that in 2.4.4 suddenly the function "skb_cow" no longer
> > returns the modified skb, but it retuns and integer for
> > succes/failure.
> >
> > This means that for networking modules requiring this function, there
> > is no source code compatibilty between 2.4.3 and 2.4.4.
>
> And skb_datarefp went away too, in fact a ton of things changes.
>
> Just deal with it.
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 */
#define CHECKSUM_NONE 0
#define CHECKSUM_HW 1
-Andi
next prev parent reply other threads:[~2001-05-11 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 9:47 Rogier Wolff
2001-05-11 9:56 ` David S. Miller
2001-05-11 10:03 ` Andi Kleen [this message]
2001-05-11 11:13 ` David S. Miller
2001-05-11 12:21 Petr Vandrovec
2001-05-11 10:32 ` 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
2001-05-11 13:08 Petr Vandrovec
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=20010511120341.A5112@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=R.E.Wolff@BitWizard.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®