From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: "Remy Bohmer" <linux@bohmer.net>
Cc: "Andrew Victor" <linux@maxim.org.za>,
"ARM Linux Mailing List"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atmel_serial: Split the interrupt handler
Date: Wed, 19 Dec 2007 14:11:00 +0100 [thread overview]
Message-ID: <20071219141100.7384aff9@dhcp-252-066.norway.atmel.com> (raw)
In-Reply-To: <3efb10970712190450p64d4e7a2k7b80d47349be9570@mail.gmail.com>
On Wed, 19 Dec 2007 13:50:16 +0100
"Remy Bohmer" <linux@bohmer.net> wrote:
> Hello Haavard,
>
> > Hmm...perhaps we can eliminate the locking in the status handler
> > too...? Does anyone see a problem with this patch?
>
> I have not seen any problem so far, besides, I am very happy with a
> lockless interrupt handling, because this helps reducing latencies.
>
> Tested it on top of the other 5 patches, and everything still works,
> also tested under stress conditions.
>
> So:
> Acked-by: Remy Bohmer <linux@bohmer.net>
Thanks. I think we can actually do it even simpler -- just check if any
of the relevant bits in pending are set, and schedule the tasklet if
they are.
Now, I suspect the locking is currently broken -- we need to guard
against updates to read_status_mask and ignore_status_mask, but I think
we can get away with only adding some locking to the tasklet, not the
interrupt handler.
Hrm. We probably need to lock while updating icount. That's a problem
since we do that from the tx interrupt handler...and I don't suppose we
want to move most of the atmel_tx_chars() code into the tasklet too...?
Haavard
next prev parent reply other threads:[~2007-12-19 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 14:14 Haavard Skinnemoen
2007-12-18 15:23 ` Remy Bohmer
2007-12-18 17:19 ` Haavard Skinnemoen
2007-12-18 19:18 ` Remy Bohmer
2007-12-19 12:34 ` Haavard Skinnemoen
2007-12-19 12:50 ` Remy Bohmer
2007-12-19 13:11 ` Haavard Skinnemoen [this message]
2007-12-19 13:18 ` Remy Bohmer
2007-12-19 13:24 ` Haavard Skinnemoen
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=20071219141100.7384aff9@dhcp-252-066.norway.atmel.com \
--to=hskinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@bohmer.net \
--cc=linux@maxim.org.za \
/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®