[lkml]   [2012]   [Feb]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCHv3 1/3] NETPOLL: Extend rx_hook support.

----- Original Message -----
> From: "Jason Wessel" <>
> To: "Andrei Warkentin" <>
> Cc:,, "Andrei Warkentin" <>,
>, "Matt Mackall" <>, "Andrei Warkentin"
> <>
> Sent: Tuesday, February 28, 2012 11:06:44 AM
> Subject: Re: [PATCHv3 1/3] NETPOLL: Extend rx_hook support.

> All that netpoll_poll() did was to call netpoll_poll_dev(). I have
> not yet looked at the differences between kgdboe and the netkdb code
> you proposed but I would have suspected it also falls victim to the
> ethernet preemption problem which prevented kgdboe from ever being
> considered for a mainline merge. Certainly there are ways to fix
> this
> problem but most involved changes to scheduling, core net code, or
> substantial driver specific changes.

I see, I read up on the issues w.r.t. preemption. Could this be worked
around by modifiying affected drivers to bypass locking if they are
used in KDB context? Make some accessor netdev-specific lock/unlocks
that won't do anything if running in KDB context.

> >
> > This is slight OT, but...are WiFi drivers sufficiently similar that
> > netpoll "just works?"
> Yes and no. Yes, you could use the NET_POLL api to transmit packets
> if the driver implemented polling hooks, but no in the sense that
> most
> of the time you need a user space driver to manage the keys which are
> time sensitive for things like WPA (usually the job of wpa
> supplicant). This is going to prevent you from having WiFi work at
> all while the kernel is in the critical exception state.

Ah right. I was thinking just open networking. I should give that a try...


 \ /
  Last update: 2012-02-28 18:47    [W:0.061 / U:0.704 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site