From: Andrei Warkentin <awarkentin@vmware.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrei Warkentin <andreiw@vmware.com>,
kgdb-bugreport@lists.sourceforge.net,
Matt Mackall <mpm@selenic.com>,
Andrei Warkentin <andrey.warkentin@gmail.com>
Subject: Re: [PATCHv3 1/3] NETPOLL: Extend rx_hook support.
Date: Thu, 1 Mar 2012 13:04:08 -0800 (PST) [thread overview]
Message-ID: <1191723499.1820816.1330635848166.JavaMail.root@zimbra-prod-mbox-2.vmware.com> (raw)
In-Reply-To: <1379096961.1660631.1330451032375.JavaMail.root@zimbra-prod-mbox-2.vmware.com>
----- Original Message -----
> From: "Andrei Warkentin" <awarkentin@vmware.com>
> To: "Jason Wessel" <jason.wessel@windriver.com>
> Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, "Andrei Warkentin" <andreiw@vmware.com>,
> kgdb-bugreport@lists.sourceforge.net, "Matt Mackall" <mpm@selenic.com>, "Andrei Warkentin"
> <andrey.warkentin@gmail.com>
> Sent: Tuesday, February 28, 2012 12:43:52 PM
> 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.
>
>
By the way, is there a good way to repro the preemption case? Hopefully this doesn't
involve some crazy hardware...
A
next prev parent reply other threads:[~2012-03-01 21:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1330137851-4716-1-git-send-email-andrey.warkentin@gmail.com>
2012-02-27 2:05 ` NetKGDB support v2 Andrei Warkentin
2012-02-27 2:05 ` [PATCHv2 1/2] NETPOLL: Extend rx_hook support Andrei Warkentin
2012-02-27 2:05 ` [PATCHv2 2/2] NETKGDB: Ethernet/UDP/IP KDB transport Andrei Warkentin
2012-02-27 3:30 ` NetKGDB v3 Andrei Warkentin
2012-02-27 3:30 ` [PATCHv3 1/3] NETPOLL: Extend rx_hook support Andrei Warkentin
2012-02-27 23:17 ` Jason Wessel
2012-02-27 23:33 ` Andrei Warkentin
2012-02-28 16:06 ` Jason Wessel
2012-02-28 17:43 ` Andrei Warkentin
2012-03-01 21:04 ` Andrei Warkentin [this message]
2012-03-01 22:24 ` Jason Wessel
2012-03-01 23:41 ` Andrei Warkentin
2012-02-27 3:30 ` [PATCHv3 2/3] NETKGDB: Ethernet/UDP/IP KDB transport Andrei Warkentin
2012-02-27 5:29 ` Valdis.Kletnieks
2012-02-27 5:36 ` Andrei Warkentin
2012-02-27 3:30 ` [PATCHv3 3/3] KGDB: Allow registering multiple I/O ops Andrei Warkentin
2012-02-27 4:38 ` NetKGDB v3 David Miller
2012-02-27 4:43 ` Andrei E. Warkentin
2012-02-28 0:04 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1191723499.1820816.1330635848166.JavaMail.root@zimbra-prod-mbox-2.vmware.com \
--to=awarkentin@vmware.com \
--cc=andreiw@vmware.com \
--cc=andrey.warkentin@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox