From: "David S. Miller" <davem@redhat.com>
To: tleete@mountain.net
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH] ipv4 skbuff locking scope
Date: Mon, 30 Oct 2000 20:03:24 -0800 [thread overview]
Message-ID: <200010310403.UAA05384@pizda.ninka.net> (raw)
In-Reply-To: <39FE39EF.62CC880B@mountain.net> (message from Tom Leete on Mon, 30 Oct 2000 22:18:07 -0500)
In-Reply-To: <39FDF518.A9F1204D@mountain.net> <200010302224.OAA02266@pizda.ninka.net> <39FE39EF.62CC880B@mountain.net>
Date: Mon, 30 Oct 2000 22:18:07 -0500
From: Tom Leete <tleete@mountain.net>
> Look, if the sleep condition test "races" due to not holding the
> lock, the schedule() just returns because if the sleep condidion
> test passes then by definition this means we were also woken up,
> see?
Would you explain what is accomplished by toggling the lock every
time through? What breaks by not doing so?
Incoming packets are not processed while the lock is held, they
get queued to the backlog. When the lock is released, the backlog
packets get processed.
For a TCP sender, these backlog packets are ACKs making room in the
send buffer so that the application can put more data into the send
buffer.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-31 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 22:24 Tom Leete
2000-10-30 22:24 ` David S. Miller
2000-10-31 2:41 ` Horst von Brand
2000-10-31 3:18 ` Tom Leete
2000-10-31 4:03 ` David S. Miller [this message]
2000-10-31 4:38 ` Albert D. Cahalan
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=200010310403.UAA05384@pizda.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=tleete@mountain.net \
/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®