From: Ravish Tayal <ravish.tayal@gmail.com>
To: linux-arm@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: sk_stream_wait_memory: Query
Date: Wed, 26 Aug 2009 19:14:23 +0530 [thread overview]
Message-ID: <e42309110908260644y65d87fc2q54405ef95be0caaf@mail.gmail.com> (raw)
Hi,
In " tcp_sendmsg" function in 2 situation, tcp code attempts to jump
to "wait_for_memory:
" case when
1. it fails to allocate to the new skb [sk_stream_alloc_pskb failure]
2. it fails to allocate new cache page.
and invokes the sk_stream_wait_memory function.
inside which it invokes the
sk_wait_event(sk, ¤t_timeo, sk_stream_memory_free(sk) &&
vm_wait);
in case if sk_stream_wait_memory is invoked due to skb allocation
failure, it would busy loop and would not relinquish the control.
[For non-preemptive kernel]
Is it fair expectation, or even this case it should let it current
task get scheduled and re try after timer expiry.
regards
Ravish Tayal
in the case if linux kernel is configured as non-premeptive
reply other threads:[~2009-08-26 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e42309110908260644y65d87fc2q54405ef95be0caaf@mail.gmail.com \
--to=ravish.tayal@gmail.com \
--cc=linux-arm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®