[lkml]   [2010]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 5/5] x86: update nr_irqs according cpu num
    On 01/08/2010 11:11 AM, Eric W. Biederman wrote:
    > Yinghai Lu <> writes:
    >> that is max number on run time.
    > Ouch! Unless I misread this code this will leave nr_irqs at
    > NR_IRQS_LEGACY. aka 16.
    > Let's do something stupid and simple.
    > nr_irqs = nr_cpus_ids * 256; /* Semi-arbitrary number */

    This would be 1048576 on the biggest machines we currently support.
    Now, the number of IRQ *vectors* is limited to
    (224-system vectors)*(cpu count), so one could argue that if there is
    anything that is not semi-arbitrary it would be that number, but that
    doesn't account for vector sharing.

    Do we have any place which requires nr_irqs to be *stable*, or can we
    simply treat it as a high water mark for IRQ numbers used?

    > Ideally we would set "nr_irqs = 0x7fffffff;" but we have just enough
    > places using nr_irqs that I think those loops would get painful if we
    > were to do that.

    Ideally we should presumably get rid of nr_irqs completely?


    H. Peter Anvin, Intel Open Source Technology Center
    I work for Intel. I don't speak on their behalf.

     \ /
      Last update: 2010-01-08 20:35    [W:0.025 / U:37.772 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site