Hello! > > And what the hell does TCP need current for anyway? > > For a very hackish user context TCP implementation that probably should > be cleaned up (but it is code freeze etc.etc.blabla.) TCP does not _use_ value of current in softirq, certainly. But it really refers to current, just because to use it before context check is the most expedient way. I see no problem to move it, if it is really a problem. Alexey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Calling current() from interrupt context John Levon
- Re: Calling current() from interrupt context Jamie Lokier
- Re: Calling current() from interrupt context yodaiken
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt context Ralf Baechle
- Re: Calling current() from interrupt context Andi Kleen
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt context Andi Kleen
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt context Andi Kleen
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt con... Andi Kleen
- Re: Calling current() from interrup... Kenn Humborg
- Re: Calling current() from interrupt context Roman Zippel
- Re: Calling current() from interrupt context Francis Galiegue
- Re: Calling current() from interrupt context Linus Torvalds
- Re: Calling current() from interrupt context Keith Owens
- Re: Calling current() from interrupt context Kenn Humborg