From: jamal <hadi@cyberus.ca>
To: Matt Carlson <mcarlson@broadcom.com>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Krishna Kumar2 <krkumar2@in.ibm.com>,
Gagan Arneja <gaagaan@gmail.com>,
netdev@vger.kernel.org, Rick Jones <rick.jones2@hp.com>,
Sridhar Samudrala <sri@us.ibm.com>,
David Miller <davem@davemloft.net>, Jeff Garzik <jeff@garzik.org>,
Michael Chan <mchan@broadcom.com>
Subject: Re: [WIP][PATCHES] Network xmit batching - tg3 support
Date: Tue, 03 Jul 2007 21:59:48 -0400 [thread overview]
Message-ID: <1183514388.5174.29.camel@localhost> (raw)
In-Reply-To: <1183491084.14005.27.camel@teletran1>
On Tue, 2007-03-07 at 12:31 -0700, Matt Carlson wrote:
> I had planned on using netperf, but pktgen sounds like a more controlled
> environment. Thanks for the tip.
I can help more if you use pktgen - netperf is more involved. Also
pktgen is much closer to the driver so it would let you see closely
if any improvements are obvious or not.
> Do you see any reason why we couldn't just add the VLAN code to the prep
> stage and simply overwrite that portion of the skb-cb? Our driver would
> just store its value in the base_flags member of tg3_tx_cbdata.
That would be a much better approach;-> Go for it.
cheers,
jamal
next prev parent reply other threads:[~2007-07-04 1:59 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 13:49 [WIP][PATCHES] Network xmit batching jamal
2007-06-07 6:16 ` Krishna Kumar2
2007-06-07 11:43 ` jamal
2007-06-07 16:13 ` Evgeniy Polyakov
2007-06-07 22:23 ` jamal
2007-06-08 8:38 ` Evgeniy Polyakov
2007-06-08 11:31 ` jamal
2007-06-08 12:09 ` Evgeniy Polyakov
2007-06-08 13:07 ` jamal
2007-06-08 21:02 ` Evgeniy Polyakov
2007-06-08 5:05 ` Krishna Kumar2
2007-06-19 13:21 ` Evgeniy Polyakov
2007-06-19 13:33 ` Evgeniy Polyakov
2007-06-19 14:00 ` Evgeniy Polyakov
2007-06-19 14:09 ` Evgeniy Polyakov
2007-06-19 16:32 ` jamal
2007-06-19 16:44 ` Evgeniy Polyakov
2007-06-19 16:28 ` jamal
2007-06-19 16:35 ` Evgeniy Polyakov
2007-06-19 16:45 ` Evgeniy Polyakov
2007-06-19 17:35 ` Robert Olsson
2007-06-19 17:48 ` jamal
2007-06-19 17:55 ` Evgeniy Polyakov
2007-06-28 0:05 ` [WIP][PATCHES] Network xmit batching - tg3 support jamal
2007-07-02 21:20 ` Matt Carlson
2007-07-03 0:21 ` Michael Chan
2007-07-03 13:26 ` jamal
2007-07-04 4:19 ` Krishna Kumar2
2007-07-04 13:22 ` jamal
2007-07-03 13:09 ` jamal
2007-07-03 19:31 ` Matt Carlson
2007-07-04 1:59 ` jamal [this message]
2007-07-03 21:30 ` David Miller
2007-06-19 22:28 ` [WIP][PATCHES] Network xmit batching David Miller
2007-06-21 15:54 ` FSCKED clock sources WAS(Re: " jamal
2007-06-21 16:08 ` jamal
2007-06-21 16:55 ` Benjamin LaHaise
2007-06-25 16:59 ` jamal
2007-06-25 17:08 ` Benjamin LaHaise
2007-06-25 17:16 ` jamal
2007-06-21 16:45 ` Evgeniy Polyakov
2007-06-25 16:58 ` jamal
2007-06-19 16:24 ` jamal
2007-06-21 21:00 ` Rick Jones
2007-06-22 9:59 ` Evgeniy Polyakov
2007-06-25 17:35 ` Rick Jones
2007-06-07 8:42 ` Krishna Kumar2
2007-06-07 12:16 ` jamal
2007-06-08 5:06 ` Krishna Kumar2
2007-06-08 11:14 ` jamal
2007-06-08 11:31 ` Krishna Kumar2
2007-06-08 11:43 ` jamal
2007-06-08 18:00 ` Rick Jones
2007-06-08 17:27 ` Rick Jones
2007-06-09 0:17 ` jamal
2007-06-09 0:40 ` Rick Jones
2007-06-07 22:42 ` jamal
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=1183514388.5174.29.camel@localhost \
--to=hadi@cyberus.ca \
--cc=Robert.Olsson@data.slu.se \
--cc=davem@davemloft.net \
--cc=gaagaan@gmail.com \
--cc=jeff@garzik.org \
--cc=johnpol@2ka.mipt.ru \
--cc=krkumar2@in.ibm.com \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=sri@us.ibm.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 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.