linux-kernel - Re: [RFC] remove netpoll receive code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071018082501.2f7023fd@freepuppy.rosehill>
Date:	Thu, 18 Oct 2007 08:25:01 -0700
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Jason Wessel <jason.wessel@...driver.com>
Subject: Re: [RFC] remove netpoll receive code

On Thu, 18 Oct 2007 00:02:44 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Wed, 17 Oct 2007 23:28:38 -0700 (PDT) David Miller <davem@...emloft.net> wrote:
> 
> > From: Stephen Hemminger <shemminger@...ux-foundation.org>
> > Date: Wed, 17 Oct 2007 13:21:31 -0700
> > 
> > > I propose that we take out all the whole netpoll rx path. If/when
> > > kgdb gets submitted a better and alternative receive path can be
> > > added.
> > 
> > I would like to kill the RX side handling of netpoll too,
> > but I don't think that's reasonable as kgdb is actively
> > being pushed for 2.6.25 inclusion.
> > 
> > Andrew is likely to add it to his -mm tree soon and therefore kgdb
> > will need to work properly now.
> 
> git-kgdb.patch has been in there for ages - maybe a year.  Although I
> disabled it a week or so ago due to the sheer number of rejects.  Will
> bring it back when things settle down a bit.
> 
> > The RX netpoll thing has a long precedence, it's been in the tree for
> > a long time, so we are in some ways stuck with it until we have a
> > complete replacement facility.  That means we can't yank it out first
> > and implement the replacement later.

How about I work on a better/alternative receive path for kgdb that
can be applied after kgdb is included.  Kgdb could actually be useful
for me :-)

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