Re: [PATCH -rt] Preemption problem in kernel RT Patch

* Beauchemin, Mark <[email protected]> wrote:

> sorry..  I sent the wrong patch file.  There was a warning in the 
> other one.

> -       int                     xmit_lock_owner;
> +#ifdef CONFIG_PREEMPT_RT
> +       void *                  xmit_lock_owner;
> +#else
> +       int                     xmit_lock_owner;
> +#endif

could you please change this to use 'current' (instead of the CPU 
number) as the xmit_lock_owner unconditionally? That results in much 
fewer #ifdefs and far cleaner code.

	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/

---

• Follow-Ups:
  • RE: [PATCH -rt] Preemption problem in kernel RT Patch
    • From: "Beauchemin, Mark" <[email protected]>

• References:
  • RE: [PATCH -rt] Preemption problem in kernel RT Patch
    • From: "Beauchemin, Mark" <[email protected]>
  • RE: [PATCH -rt] Preemption problem in kernel RT Patch
    • From: "Beauchemin, Mark" <[email protected]>

• Prev by Date: Re: Linux Kernel cfs scheduler and xorg kbd
• Next by Date: Re: [PATCH] pci_get_device call from interrupt in reboot fixups
• Previous by thread: RE: [PATCH -rt] Preemption problem in kernel RT Patch
• Next by thread: RE: [PATCH -rt] Preemption problem in kernel RT Patch
• Index(es):
  • Date
  • Thread

[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]