From: "David S. Miller" <davem@redhat.com>
To: girouard@us.ibm.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: patch for common networking error messages
Date: Tue, 17 Jun 2003 14:14:43 -0700 (PDT) [thread overview]
Message-ID: <20030617.141443.24610277.davem@redhat.com> (raw)
In-Reply-To: <OFDF06338E.06BC4D08-ON85256D48.00729284@us.ibm.com>
From: Janice Girouard <girouard@us.ibm.com>
Date: Tue, 17 Jun 2003 15:57:59 -0500
Did I understand:
> 1) Chip has a "flow cache", LRU based, managed like routing caches
You need the chip to support your technique.
No shit Sherlock.
But it should be noted that the idea can be fully verified in software
by adding the scheme into the RX processing of some existing ethernet
driver.
Are the vendors picking up on this?
If they're going to ignore my ideas, that's not my problem.
I still don't see how this gets rid of the copy_to_user space once
you've gathered the buffers. How do you feed the user buffer addresses to
the card?
You flip the pages into userspace, ie. you replace the page the user
currently has with the one the networking buffer is using.
What technique are you using? Is it proprietary?
ROFL!
next prev parent reply other threads:[~2003-06-17 21:14 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 20:57 patch for common networking error messages Janice Girouard
2003-06-17 21:14 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-17 20:40 Janice Girouard
2003-06-17 20:42 ` David S. Miller
2003-06-17 2:12 Janice Girouard
2003-06-17 4:34 ` Valdis.Kletnieks
2003-06-17 16:08 ` Stephen Hemminger
2003-06-17 16:09 ` David S. Miller
2003-06-17 18:46 ` Jeff Garzik
2003-06-17 19:06 ` Janice M Girouard
2003-06-17 19:23 ` Jeff Garzik
2003-06-17 19:46 ` Janice M Girouard
2003-06-17 19:50 ` David S. Miller
2003-06-17 20:24 ` Janice M Girouard
2003-06-17 20:27 ` David S. Miller
2003-06-17 0:44 Janice Girouard
2003-06-17 1:19 ` David S. Miller
2003-06-17 14:34 ` Mr. James W. Laferriere
2003-06-16 22:50 Janice Girouard
2003-06-16 22:55 ` David S. Miller
2003-06-21 12:36 ` Alan Cox
2003-06-21 14:27 ` Jamal Hadi
2003-06-23 0:46 ` David S. Miller
2003-06-23 11:54 ` Alan Cox
2003-06-16 22:29 Janice Girouard
2003-06-16 22:27 ` David S. Miller
2003-06-16 22:45 ` Nivedita Singhvi
2003-06-16 22:52 ` David S. Miller
2003-06-17 0:07 ` Nivedita Singhvi
2003-06-16 20:30 Janice M Girouard
2003-06-16 20:38 ` David S. Miller
2003-06-16 20:53 ` Andi Kleen
2003-06-16 20:51 ` David S. Miller
2003-06-16 22:27 ` Andrew Morton
2003-06-17 7:09 ` Andi Kleen
2003-06-17 7:20 ` Andrew Morton
2003-06-16 20:59 ` Janice M Girouard
2003-06-16 22:48 ` Jeff Garzik
2003-06-16 22:52 ` Jeff Garzik
2003-06-16 22:13 ` Nivedita Singhvi
2003-06-16 22:13 ` David S. Miller
2003-06-16 22:50 ` Nivedita Singhvi
2003-06-16 22:57 ` David S. Miller
2003-06-16 23:02 ` Donald Becker
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=20030617.141443.24610277.davem@redhat.com \
--to=davem@redhat.com \
--cc=girouard@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).