From: David Daney <ddaney@caviumnetworks.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org,
netdev@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 4/4] Staging: Octeon: Free transmit SKBs in a timely manner.
Date: Mon, 15 Feb 2010 12:41:03 -0800 [thread overview]
Message-ID: <4B79B15F.7030506@caviumnetworks.com> (raw)
In-Reply-To: <1266265673.2859.5.camel@edumazet-laptop>
On 02/15/2010 12:27 PM, Eric Dumazet wrote:
> Le lundi 15 février 2010 à 12:13 -0800, David Daney a écrit :
>> If we wait for the once-per-second cleanup to free transmit SKBs,
>> sockets with small transmit buffer sizes might spend most of their
>> time blocked waiting for the cleanup.
>>
>> Normally we do a cleanup for each transmitted packet. We add a
>> watchdog type timer so that we also schedule a timeout for 150uS after
>> a packet is transmitted. The watchdog is reset for each transmitted
>> packet, so for high packet rates, it never expires. At these high
>> rates, the cleanups are done for each packet so the extra watchdog
>> initiated cleanups are not needed.
>
> s/needed/fired/
>
or perhaps s/are not needed/are neither needed nor fired/
> Hmm, but re-arming a timer for each transmited packet must have a cost ?
>
The cost is fairly low (less than 10 processor clock cycles). We didn't
add this for amusement, people actually do things like only send UDP
packets from userspace. Since we can fill the transmit queue faster
than it is emptied, the socket transmit buffer is quickly consumed. If
we don't free the SKBs in short order, the transmitting process get to
take a long sleep (until our previous once per second clean up task was
run).
>>
>> Signed-off-by: David Daney<ddaney@caviumnetworks.com>
>
> Is there any particular reason periodic is spelled preiodic ?
Ha! No good reason. I will correct the spelling.
Thanks,
David Daney
>
>> ---
>> }
>>
>> -static void cvm_oct_tx_clean_worker(struct work_struct *work)
>> +static void cvm_oct_preiodic_worker(struct work_struct *work)
>> {
>
>
>
>> - INIT_DELAYED_WORK(&priv->tx_clean_work,
>> - cvm_oct_tx_clean_worker);
>> -
>> + INIT_DELAYED_WORK(&priv->port_periodic_work,
>> + cvm_oct_preiodic_worker);
>
>
>
>
next prev parent reply other threads:[~2010-02-15 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 20:12 [PATCH 0/4] Improvements to octeon_ethernet David Daney
2010-02-15 20:13 ` [PATCH 1/4] Staging: octeon: remove unneeded includes David Daney
2010-02-17 14:17 ` Ralf Baechle
2010-02-15 20:13 ` [PATCH 2/4] Staging: Octeon: Run phy bus accesses on a workqueue David Daney
2010-02-17 14:17 ` Ralf Baechle
2010-02-15 20:13 ` [PATCH 3/4] MIPS: Octeon: Do proper acknowledgment of CIU timer interrupts David Daney
2010-02-17 14:17 ` Ralf Baechle
2010-02-15 20:13 ` [PATCH 4/4] Staging: Octeon: Free transmit SKBs in a timely manner David Daney
2010-02-15 20:27 ` Eric Dumazet
2010-02-15 20:41 ` David Daney [this message]
2010-02-15 21:11 ` Eric Dumazet
2010-02-15 22:05 ` David Daney
2010-02-15 23:06 ` [PATCH 4/4] Staging: Octeon: Free transmit SKBs in a timely manner (v2) David Daney
2010-02-17 14:17 ` Ralf Baechle
2010-02-15 21:05 ` [PATCH 0/4] Improvements to octeon_ethernet Greg KH
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=4B79B15F.7030506@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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