netdev - Re: [PATCH] TX_RING and packet mmap

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: <alpine.DEB.1.10.0904211642320.31780@qirst.com>
Date:	Tue, 21 Apr 2009 16:43:16 -0400 (EDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Johann Baudy <johann.baudy@...-log.net>
cc:	netdev@...r.kernel.org, Evgeniy Polyakov <zbr@...emap.net>
Subject: Re: [PATCH] TX_RING and packet mmap

On Tue, 21 Apr 2009, Johann Baudy wrote:

> >> Could you clean then states up a bit to reflect what they actually mean?
> >>
> >> TP_STATUS_AVAILABLE             => Frame is available
> >> TP_STATUS_SEND_REQUEST          => Frame waits for sending
> >> TP_STATUS_SENDING               => Frame is being sent.
> >
> > Ok
>
> Do you suggest to replace previous TP_STATUS_KERNEL with TP_STATUS_AVAILABLE?
> or Add a new status?

Well yes. But I guess you know best what to call them. Just make them
more decriptive of their function.