linux-kernel - Re: [PATCH] net_dma: call dmaengine_get only if NET

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] [day] [month] [year] [list]

Message-Id: <20090206.220531.81492830.davem@davemloft.net>
Date:	Fri, 06 Feb 2009 22:05:31 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	dan.j.williams@...el.com
Cc:	anemo@....ocn.ne.jp, maciej.sosnowski@...el.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] net_dma: call dmaengine_get only if NET_DMA enabled

From: Dan Williams <dan.j.williams@...el.com>
Date: Fri, 06 Feb 2009 23:03:11 -0700

> David Miller wrote:
> > From: David Miller <davem@...emloft.net>
> > Date: Fri, 06 Feb 2009 19:29:10 -0800 (PST)
> > 
> >> From: Dan Williams <dan.j.williams@...el.com>
> >> Date: Fri, 6 Feb 2009 15:52:35 -0700
> >>
> >>> Yes, it has been on the todo list for a while, but I eventually want
> >>> the net case to look more like the raid case.  I.e. have one code path
> >>> that picks async versus sync at runtime, with the option to compile
> >>> out async support with header file ifdefs only.
> >> And how does any of that get us any closer to a fix right now
> >> for this problem that doesn't require an ifdef?
> >>
> >> Someone please work on this.
> > I guess that'd end up being me....
> 
> Not necessarily, you did snap me back into reality with that comment.
> 
> > How about something like this?
> 
> Looks good.

Ok, I'll add this to net-2.6 then, thanks.
--
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/