lkml.org 
[lkml]   [2005]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: RFC: i386: kill !4KSTACKS
    Date
    Andi Kleen wrote:

    > AFAIK with interrupt stacks it shouldn't be a big issue to switch
    > to a private bigger stack. ndiswrapper just needs to have its own private
    > way to do "current" which accesses thread_info at the bottom of the stack.

    I am developer of ndiswrapper and just caught up with this discussion. I am
    interested in providing private stack for ndiswrapper. I am not familiar
    with linux kernel internals to understand your proposal. Could you give me
    details please: If you can give a rough sketch of idea, I can implement it.
    Better yet, if you (or anyone else) can provide an implementation (not
    necessarily against ndsiwrapper, but a proof of concept), it will be
    greatly appreciated - this should also help any other projects that need
    more than 4k stack.

    Thanks,
    Giri.



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

    \
     
     \ /
      Last update: 2005-09-06 15:34    [W:4.818 / U:1.184 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site