From: Radha Mohan <radhamohan_ch@yahoo.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: Re: behavior of TSO in kernel
Date: Sat, 6 Jun 2009 19:41:21 +0530 (IST) [thread overview]
Message-ID: <171835.76446.qm@web94811.mail.in2.yahoo.com> (raw)
In-Reply-To: <20090605.182038.133831345.davem@davemloft.net>
>The TSO engine of the networking has been rewritten at least
>3 times since 2.6.15
Thank you for the info.
Actually we are working on an SoC and we just started moving from kernel 2.6.15, so can you tell me from which kernel version the latest TSO engine is being used. That'll make our life easier and avoid moving kernels frequently. Currently we are thinking of moving to 2.6.24. Will that do??
Explore and discover exciting holidays and getaways with Yahoo! India Travel http://in.travel.yahoo.com/
next prev parent reply other threads:[~2009-06-06 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 14:39 behavior of TSO in kernel Radha Mohan
2009-06-06 1:20 ` David Miller
2009-06-06 14:11 ` Radha Mohan [this message]
2009-06-09 8:01 ` Ilpo Järvinen
-- strict thread matches above, loose matches on Subject: below --
2009-06-29 6:44 Radha Mohan
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=171835.76446.qm@web94811.mail.in2.yahoo.com \
--to=radhamohan_ch@yahoo.com \
--cc=davem@davemloft.net \
--cc=netdev@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).