netdev - Re: [PATCH net-next v5] Add support of Cavium Liquidio ethernet adapters

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]

Date:	Thu, 19 Feb 2015 16:21:47 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	Derek.Chickles@...iumnetworks.com
Cc:	Raghu.Vatsavayi@...iumnetworks.com, netdev@...r.kernel.org,
	Satananda.Burla@...iumnetworks.com,
	Felix.Manlunas@...iumnetworks.com
Subject: Re: [PATCH net-next v5] Add support of Cavium Liquidio ethernet
 adapters

From: "Chickles, Derek" <Derek.Chickles@...iumnetworks.com>
Date: Thu, 19 Feb 2015 20:44:11 +0000

>> From: David Miller [mailto:davem@...emloft.net]
>> Sent: Thursday, February 19, 2015 11:36 AM
>> To: Vatsavayi, Raghu
>> Cc: netdev@...r.kernel.org; Chickles, Derek; Burla, Satananda; Manlunas,
>> Felix; Vatsavayi, Raghu
>> Subject: Re: [PATCH net-next v5] Add support of Cavium Liquidio ethernet
>> adapters
>> 
>> From: Raghu Vatsavayi <rvatsavayi@...iumnetworks.com>
>> Date: Wed, 11 Feb 2015 17:20:42 -0800
>> 
>> > +	pci_unmap_single(lio->oct_dev->pci_dev, finfo->dptr, skb->len,
>> > +			 PCI_DMA_TODEVICE);
>> 
>> Please use the dma_*() variants of the DMA interfaces for which you
>> will pass in a reference to the struct device embedded in the pci_dev.
>> 
>> This will allow you to later make use of various generic facilities
>> we will build for DMA mapping SKBs in the networking, allocating
>> networknig page frags, etc.
>> 
> 
> You said you *will* be building these facilities. Are there any now
> that we can take advantage of? (We'll move to the dma_* variants
> regardless.)

There is a page frag allocator that the ENIC guys wrote which I've
asked them to make completely generic before inclusion.

> Also, do you have any remaining style / global comments that we should
> address?

I will re-review the driver after you make another spin.

It is extremely time intensive to walk over your driver beacuse it
is so huge, so those of us who are actually trying to help you by
reviewing your code have to do it piecemeal.

So asking us to look into "everything" is not really all that tenable.

This is going to be a long process and it's going to take time, and
it's important to understand that people are volunteering their time
to do these reviews.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html