Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1283183

Re: linux-next: build failure after merge of the block tree

From Christoph Hellwig <hch@lst.de>
Newsgroups linux.kernel
Subject Re: linux-next: build failure after merge of the block tree
Date 2015-12-03 17:50 +0100
Message-ID <qBFeW-7CN-15@gated-at.bofh.it> (permalink)
References (5 earlier) <qByQa-3g4-19@gated-at.bofh.it> <qByQa-3g4-21@gated-at.bofh.it> <qByZP-3zg-5@gated-at.bofh.it> <qBzjc-3FV-11@gated-at.bofh.it> <qBzVU-4ak-19@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Dec 03, 2015 at 12:07:23PM +0100, Matias Bjørling wrote:
> What is the reason to keep the nvme_ns internally to the nvme core?
>
> We can definitely move ->nsid and the lba_shift into nvm_dev. Only thing I 
> have is that it moves a small part of nvme logic into the lightnvm core.

It's a structure specific to the NVM command set, and the block device
use to implement it in Linux.  Similar to how you wouldn't use the SCSI
disk driver data structures to implement the tape driver for example.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

linux-next: build failure after merge of the block tree Mark Brown <broonie@kernel.org> - 2015-12-02 17:20 +0100
  Re: linux-next: build failure after merge of the block tree Christoph Hellwig <hch@lst.de> - 2015-12-02 17:50 +0100
    Re: linux-next: build failure after merge of the block tree Jens Axboe <axboe@kernel.dk> - 2015-12-02 22:10 +0100
      Re: linux-next: build failure after merge of the block tree Keith Busch <keith.busch@intel.com> - 2015-12-02 22:20 +0100
        Re: linux-next: build failure after merge of the block tree Jens Axboe <axboe@kernel.dk> - 2015-12-02 22:40 +0100
          Re: linux-next: build failure after merge of the block tree Christoph Hellwig <hch@lst.de> - 2015-12-03 08:40 +0100
      Re: linux-next: build failure after merge of the block tree Matias Bjørling <m@bjorling.me> - 2015-12-03 09:40 +0100
        Re: linux-next: build failure after merge of the block tree Christoph Hellwig <hch@lst.de> - 2015-12-03 10:10 +0100
          Re: linux-next: build failure after merge of the block tree Christoph Hellwig <hch@lst.de> - 2015-12-03 11:00 +0100
            Re: linux-next: build failure after merge of the block tree Matias Bjørling <m@bjorling.me> - 2015-12-03 11:10 +0100
              Re: linux-next: build failure after merge of the block tree Christoph Hellwig <hch@lst.de> - 2015-12-03 11:30 +0100
                Re: linux-next: build failure after merge of the block tree Matias Bjørling <m@bjorling.me> - 2015-12-03 12:10 +0100
                Re: linux-next: build failure after merge of the block tree Christoph Hellwig <hch@lst.de> - 2015-12-03 17:50 +0100
                Re: linux-next: build failure after merge of the block tree Matias Bjørling <m@bjorling.me> - 2015-12-04 13:20 +0100
          Re: linux-next: build failure after merge of the block tree Matias Bjørling <m@bjorling.me> - 2015-12-03 11:00 +0100

csiph-web