From: Chris Friesen <cfriesen@nortelnetworks.com>
To: davem@redhat.com
Cc: netdev@oss.sgi.com
Subject: copybreak and gige network drivers
Date: Mon, 29 Sep 2003 14:25:12 -0400 [thread overview]
Message-ID: <3F787908.7000305@nortelnetworks.com> (raw)
I'm looking at doing some work on a driver for the gige portion of the
Marvell Disco2.
The existing driver allocates mtu-sized buffers and always passes them
off to the network stack. I'm thinking about adding some copybreak
optimizations, but I'm not sure what value I should use for the
copybreak. I would expect most packets to be on the smaller side.
Any suggestions?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2003-09-29 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 18:25 Chris Friesen [this message]
2003-09-29 23:14 ` copybreak and gige network drivers Donald Becker
2003-09-30 14:39 ` Chris Friesen
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=3F787908.7000305@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=davem@redhat.com \
--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).