From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: jens axboe <jens.axboe@oracle.com>,
netdev@vger.kernel.org, nickpiggin@yahoo.com.au,
ilpo jarvinen <ilpo.jarvinen@helsinki.fi>
Subject: Re: [PATCH 1/2]: softirq: Add support for triggering softirq work on softirqs.
Date: Fri, 19 Sep 2008 09:57:30 -0700 (PDT) [thread overview]
Message-ID: <31089112.38051221843450562.JavaMail.root@tahiti.vyatta.com> (raw)
In-Reply-To: <20080918.023614.193687634.davem@davemloft.net>
I wonder if the added overhead of local_irq_disable/local_irq_enable is
killing any performance gain. Certainly it adds more latency to a sensitive code path.
Is there a good lock-less solution?
next prev parent reply other threads:[~2008-09-19 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 2:34 [PATCH 1/2]: softirq: Add support for triggering softirq work on softirqs David Miller
2008-09-18 4:35 ` Jens Axboe
2008-09-18 4:50 ` David Miller
2008-09-18 7:40 ` Ilpo Järvinen
2008-09-18 9:36 ` David Miller
2008-09-19 16:57 ` Stephen Hemminger [this message]
2008-09-19 20:29 ` David Miller
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=31089112.38051221843450562.JavaMail.root@tahiti.vyatta.com \
--to=stephen.hemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=jens.axboe@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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).