* Alexey Kuznetsov <[email protected]> wrote:
> > also, the "be afraid of the hardirq or the process context" mantra
> > is overblown as well. If something is too heavy for a hardirq, _it's
> > too heavy for a tasklet too_. Most hardirqs are (or should be)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > running with interrupts enabled, which makes their difference to
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > softirqs miniscule.
^^^^^^^^^^^^^^^^^^
>
> Incorrect.
>
> The difference between softirqs and hardirqs lays not in their
> "heavyness". It is in reentrancy protection, which has to be done with
> local_irq_disable(), unless networking is not isolated from hardirqs.
i know that pretty well ;)
> That's all. Networking is too hairy to allow to be executed with
> disabled hardirqs. And moving this hairyiness to process context
> requires <irony mode> a little </> more efforts than conversion
> tasklets to work queues.
as i said above (see the underlined sentence), hardirq contexts already
run just fine with hardirqs enabled. So your dismissal of executing that
'hairy' bit in hardirq context is not that automatically true as you
seem to assume i think.
also, network softirq locking dependencies arent all that magic or
complex either: they do not operate on sockets that are already locked
by a user context, they are per CPU and they are not preempted by
'themselves', nor are they preempted by certain other softirqs (such as
they are not preempted by the timer softirq). Am i missing some point of
yours?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
