All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: CPU processing time between using TCP and UDP
Date: Tue, 07 Feb 2012 15:30:44 +0000	[thread overview]
Message-ID: <4F3143A4.8050506@workingcode.com> (raw)
In-Reply-To: <CADa7JjUrtiQF=bBm--a1WLBFSW877_=Ws95Z+rDpwhaWnXBuyg@mail.gmail.com>

Srinidhi M wrote:
> Could you please let me know, which module in TCP/IP is consuming more
> time than UDP? How can we reduce packet processing time when sending
> through TCP stack? Please let me know your thoughts.

Are you sure you wanted to post this message on the Linux PPP mailing list?

Anyway, without knowing a lot about your application, how you're
measuring things, and what environment you're running in, it's a little
hard to guess at what sort of change you might require.  But I'll give
it a try.

Have you tried setting the TCP_NODELAY option and/or redesigning around
TCP_CORK?  If your application does a lot of tiny write(2) calls, you
will sometimes see RTT delays in delivery.  This is normal, and it's
something that the stack does in order to protect the network against
misbehaving (or just inefficient) applications.  You can disable it in
order to force a write(2) to result in a transmission ... but be careful
if you do this, because doing so can result in a flood of tiny packets
if you (say) write a byte at a time.

Have you considered SCTP instead?  If you have a message-oriented
protocol (rather than a stream-oriented one), and you need reliable
delivery, SCTP may be a better option for you than TCP.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  reply	other threads:[~2012-02-07 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 14:53 CPU processing time between using TCP and UDP Srinidhi M
2012-02-07 15:30 ` James Carlson [this message]
2012-02-07 18:55 ` terry white
2012-02-08 11:55 ` Srinidhi M
  -- strict thread matches above, loose matches on Subject: below --
2012-02-07 10:25 Srinidhi M

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=4F3143A4.8050506@workingcode.com \
    --to=carlsonj@workingcode.com \
    --cc=linux-ppp@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 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.