From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [UPDATE] Zerocopy patches, against 2.4.1-pre10
Date: Thu, 25 Jan 2001 01:29:08 -0800 (PST) [thread overview]
Message-ID: <14959.61924.48548.388874@pizda.ninka.net> (raw)
In-Reply-To: <3A6F8415.8EC5DB23@uow.edu.au>
In-Reply-To: <200101242123.NAA00986@pizda.ninka.net> <3A6F8415.8EC5DB23@uow.edu.au>
Andrew Morton writes:
> What I suggest we do here is to add a new flag to the per-device
> table `HAS_HWCKSM' and use that to set the device capabilities,
> rather than using the IS_CYCLONE stuff. Then we can add cards
> individually as confirmation comes in.
This idea sounds just fine.
> I do have a 200-line 3c59x patch banked up - it does the following:
...
> So... How to coordinate these diffs? I'd propose that I implement
> the HAS_HWCKSM thing, test zerocopy with it on the five NICs which
> I have. Then what? Ask Linus to merge the non-zc parts?
I have a better idea. Look, all the dev->features and flag names are
in the kernel tree already. The only thing which hasn't propagated
which the driver will reference are the skb frag things. This code
referencing the skb frags in the 3c59x hard_start_xmit method you can
just protect with #ifdef MAX_SKB_FRAGS or similar. See?
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-25 9:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200101242123.NAA00986@pizda.ninka.net>
2001-01-25 1:40 ` [UPDATE] Zerocopy patches, against 2.4.1-pre10 Andrew Morton
2001-01-25 19:29 ` kuznet
2001-01-25 20:28 ` Ion Badulescu
2001-01-25 20:36 ` kuznet
2001-01-25 20:43 ` David S. Miller
2001-01-25 21:11 ` Ion Badulescu
2001-01-26 19:43 ` kuznet
2001-01-29 22:02 ` David S. Miller
2001-01-25 21:14 ` David S. Miller
2001-01-25 21:29 ` Steve Whitehouse
2001-01-31 16:04 ` Alan Cox
2001-03-11 20:55 ` NBD Fix (attempt #2) Steve Whitehouse
2001-01-25 21:38 ` [UPDATE] Zerocopy patches, against 2.4.1-pre10 David S. Miller
2001-01-26 6:06 ` Ion Badulescu
2001-01-26 13:13 ` David S. Miller
2001-01-26 20:43 ` Ion Badulescu
2001-01-27 0:55 ` Ion Badulescu
2001-01-27 18:39 ` kuznet
2001-01-27 21:18 ` Ion Badulescu
2001-01-30 6:02 ` David S. Miller
2001-01-26 1:27 ` Andrew Morton
2001-01-25 9:29 ` David S. Miller [this message]
2001-01-24 21:52 Jonathan Earle
2001-01-24 23:33 ` Peter Samuelson
-- strict thread matches above, loose matches on Subject: below --
2001-01-24 21:34 Jonathan Earle
2001-01-24 21:45 ` Mathieu Chouquet-Stringer
2001-01-31 22:42 ` Rogerio Brito
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=14959.61924.48548.388874@pizda.ninka.net \
--to=davem@redhat.com \
--cc=andrewm@uow.edu.au \
--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;
as well as URLs for NNTP newsgroup(s).