[PATCH 3/7] null_blk: refactor to support non-gendisk devices

With LightNVM enabled devices, the gendisk structure is not exposed to the user. This hides the device driver specific sysfs entries, and prevents binding of LightNVM geometry information to the device. Refactor the device registration process, so that gendisk and non-gendisk devices are easily

[PATCH 6/7] lightnvm: expose device geometry through sysfs

From: "Simon A. F. Lund" For a host to access an Open-Channel SSD, it has to know its geometry, so that it writes and reads at the appropriate device bounds. Currently, the geometry information is kept within the kernel, and not exported to user-space for consumption. This

[PATCH 1/7] lightnvm: NVM should depend on HAS_DMA

From: Geert Uytterhoeven If NO_DMA=y: drivers/built-in.o: In function `nvme_nvm_dev_dma_free': lightnvm.c:(.text+0x23df1a): undefined reference to `dma_pool_free' drivers/built-in.o: In function `nvme_nvm_dev_dma_alloc': lightnvm.c:(.text+0x23df38):

[GIT PULL 0/7] LightNVM pull request for 4.9

Hi Jens, A couple of patches for 4.9. We are preparing the pblk target for upstream, but it will have to wait for at least a cycle before it is ready. Geert and Arnd sent two fixes. One check for DMA and another for missing a device_add check. Simon added sysfs support to LightNVM. It allows

Re: [PATCHv3 29/41] ext4: make ext4_mpage_readpages() hugepage-aware

On Thu, Sep 15, 2016 at 02:55:11PM +0300, Kirill A. Shutemov wrote: > This patch modifies ext4_mpage_readpages() to deal with huge pages. > > We read out 2M at once, so we have to alloc (HPAGE_PMD_NR * > blocks_per_page) sector_t for that. I'm not entirely happy with kmalloc > in this codepath,

Re: [PATCHv3 07/41] mm, shmem: swich huge tmpfs to multi-order radix-tree entries

On Thu, Sep 15, 2016 at 02:54:49PM +0300, Kirill A. Shutemov wrote: > We would need to use multi-order radix-tree entires for ext4 and other > filesystems to have coherent view on tags (dirty/towrite) in the tree. > > This patch converts huge tmpfs implementation to multi-order entries, so > we

Re: [PATCH] lightnvm: propagate device_add() error code

On 09/15/2016 05:53 PM, Arnd Bergmann wrote: device_add() may fail, and all callers are supposed to check the return value, but one new user in lightnvm doesn't: drivers/lightnvm/sysfs.c: In function 'nvm_sysfs_register_dev': drivers/lightnvm/sysfs.c:184:2: error: ignoring return value of

Re: [PATCH 6/6] media/cobalt: use pci_irq_allocate_vectors

On Fri, Sep 16, 2016 at 10:01:42AM +0200, Hans Verkuil wrote: > PCI_IRQ_MSI is unknown, I assume that this will appear in 4.9? The flag is in 4.8-rc. -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majord...@vger.kernel.org More majordomo info

Re: [PATCH 6/6] media/cobalt: use pci_irq_allocate_vectors

Hi Christoph, On 09/11/2016 03:31 PM, Christoph Hellwig wrote: > Simply the interrupt setup by using the new PCI layer helpers. > > Despite using pci_enable_msi_range, this driver was only requesting a > single MSI vector anyway. > > Signed-off-by: Christoph Hellwig > --- >