linux-kernel - Re: [PATCH 0/4] New firewire stack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Dec 2006 12:29:15 -0300
From:	Pieter Palmers <pieterp@...w.be>
To:	Kristian Høgsberg <krh@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux1394-devel@...ts.sourceforge.net
Subject: Re: [PATCH 0/4] New firewire stack - updated patches

Kristian Høgsberg wrote:
> Hi,
> 
> Here's a new set of patches for the new firewire stack.  The changes
> since the last set of patches address the issues that were raised on
> the list and can be reviewed in detail here:
.. for some reason I didn't get patch 3/4 and 4/4 on the linux1394-devel 
list, so I'll reply to this one.

I would suggest a reordering of the interrupt flag checks. Currently the 
interrupts that are least likely to occur are checked first. I don't see 
why. I would reorder the check such that ISO interrupts are checked 
first, as they have the most stringent timing constraints and are most 
likely to occur (when using ISO traffic).

After processing the ISO interrupts (and maybe the Async ones), a bypass 
could be inserted to exit the interrupt handler when there are no other 
interrupts to be handled. All other interrupts are to report relatively 
rare events or errors (error handling still to be added I assume). The 
effective run-length of the interrupt handler would be shorter using 
such a bypass, especially in the case where there is a lot of ISO traffic.

I'm looking forward to your ISO implementation, and I hope to 
incorporate it into FreeBob really fast.

Pieter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/