From: "David S. Miller" <davem@davemloft.net>
To: ravinandan.arakali@neterion.com
Cc: jgarzik@pobox.com, netdev@oss.sgi.com,
raghavendra.koushik@neterion.com, leonid.grossman@neterion.com,
ananda.raju@neterion.com, rapuru.sriram@neterion.com
Subject: Re: [PATCH 2.6.12-rc4] IPv4/IPv6: UDP Large Send Offload feature
Date: Thu, 02 Jun 2005 16:22:04 -0700 (PDT) [thread overview]
Message-ID: <20050602.162204.68041633.davem@davemloft.net> (raw)
In-Reply-To: <003201c567c9$73322240$3910100a@pc.s2io.com>
From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
Date: Thu, 2 Jun 2005 16:18:55 -0700
> Since there seems to be pros and cons for both the approaches, we are
> planning
> to submit two separate patches(one for each approach). These patches also
> include the ethtool changes. In terms of performance, we did not observe any
> diff between the two approaches although the first approach(using SG)
> minimizes
> coalescing in driver.
Ok. I think minimizing driver specific work is probably going
to make the SG approach more desirable, but we'll see.
> Also, some changes will be required in the ethtool user-level utility.
> I'm not sure if this is the right forum to submit patches for the ethtool
> utility as well..
Making sure jgarzik@pobox.com gets the patch is usually the way
to go wrt. ethtool submissions.
next prev parent reply other threads:[~2005-06-02 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 23:20 [PATCH 2.6.12-rc4] IPv4/IPv6: UDP Large Send Offload feature ravinandan.arakali
2005-05-26 23:37 ` David S. Miller
2005-05-26 23:42 ` David S. Miller
2005-05-27 16:32 ` Ravinandan Arakali
2005-05-27 19:02 ` David S. Miller
2005-06-02 23:18 ` Ravinandan Arakali
2005-06-02 23:22 ` David S. Miller [this message]
2005-05-27 15:57 ` Stephen Hemminger
2005-05-27 19:03 ` David S. Miller
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=20050602.162204.68041633.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ananda.raju@neterion.com \
--cc=jgarzik@pobox.com \
--cc=leonid.grossman@neterion.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@neterion.com \
--cc=rapuru.sriram@neterion.com \
--cc=ravinandan.arakali@neterion.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.