On 6 Jun 2016 at 7:38, David Brown wrote:
> On Fri, Jun 03, 2016 at 07:42:52PM +0200, Emese Revfy wrote:
> >On Wed, 1 Jun 2016 12:42:27 -0700
> >Andrew Morton wrote:
> >
> >> I don't think I'm really understanding. Won't this produce the same
> >> value on each and every boot?
> >
> >No, because
On 01/06/16 16:54, Vincent Guittot wrote:
> On 1 June 2016 at 17:31, Dietmar Eggemann wrote:
>> On 30/05/16 16:52, Vincent Guittot wrote:
>>> The cfs_rq->avg.last_update_time is initialize to 0 with the main effect
>>> that the 1st sched_entity that will be attached, will keep its
>>
>> attached i
On 6/6/2016 3:31 PM, Dan Williams wrote:
> On Mon, Jun 6, 2016 at 12:25 PM, Linda Knippers
> wrote:
>> On 6/4/2016 4:52 PM, Dan Williams wrote:
>>> There are scenarios where we need a middle ground between disabling all
>>> manual bind/unbind attempts (via driver->suppress_bind_attrs) and
>>> a
On Mon, Jun 6, 2016 at 12:31 PM, Dan Williams wrote:
> On Mon, Jun 6, 2016 at 12:25 PM, Linda Knippers
> wrote:
>> On 6/4/2016 4:52 PM, Dan Williams wrote:
>>> There are scenarios where we need a middle ground between disabling all
>>> manual bind/unbind attempts (via driver->suppress_bind_attrs
On Mon, Jun 6, 2016 at 12:36 PM, Linda Knippers wrote:
>
>
> On 6/6/2016 3:31 PM, Dan Williams wrote:
>> On Mon, Jun 6, 2016 at 12:25 PM, Linda Knippers
>> wrote:
>>> On 6/4/2016 4:52 PM, Dan Williams wrote:
There are scenarios where we need a middle ground between disabling all
manual
There is currently no modular user of this function. We used to have
filesystems that open-coded the page cache instantiation, but luckily
they're all streamlined, and we don't want this to come back.
Signed-off-by: Johannes Weiner
---
mm/swap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a
Currently, scan pressure between the anon and file LRU lists is
balanced based on a mixture of reclaim efficiency and a somewhat vague
notion of "value" of having certain pages in memory over others. That
concept of value is problematic, because it has caused us to count any
event that remotely mak
Hi everybody,
this series re-implements the LRU balancing between page cache and
anonymous pages to work better with fast random IO swap devices.
The LRU balancing code evolved under slow rotational disks with high
seek overhead, and it had to extrapolate the cost of reclaiming a list
based on in
Currently, THP are counted as single pages until they are split right
before being swapped out. However, at that point the VM is already in
the middle of reclaim, and adjusting the LRU balance then is useless.
Always account THP by the number of basepages, and remove the fixup
from the splitting p
Operations like MADV_FREE, FADV_DONTNEED etc. currently move any
affected active pages to the inactive list to accelerate their reclaim
(good) but also steer page reclaim toward that LRU type, or away from
the other (bad).
The reason why this is undesirable is that such operations are not
part of
- On May 30, 2016, at 9:18 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On May 27, 2016, at 5:16 PM, Julien Desfossez jdesfos...@efficios.com
> wrote:
>
>> This tracepoint allows to keep track of all priority changes made by all
>> sites that can change this value. The
Since the LRUs were split into anon and file lists, the VM has been
balancing between page cache and anonymous pages based on per-list
ratios of scanned vs. rotated pages. In most cases that tips page
reclaim towards the list that is easier to reclaim and has the fewest
actively used pages, but the
When the splitlru patches divided page cache and swap-backed pages
into separate LRU lists, the pressure balance between the lists was
biased to account for the fact that streaming IO can cause memory
pressure with a flood of pages that are used only once. New page cache
additions would tip the bal
Isolating an existing LRU page and subsequently putting it back on the
list currently influences the balance between the anon and file LRUs.
For example, heavy page migration or compaction could influence the
balance between the LRUs and make one type more attractive when that
type of page is affec
They're the same function, and for the purpose of all callers they are
equivalent to lru_cache_add().
Signed-off-by: Johannes Weiner
---
fs/cifs/file.c | 10 +-
fs/fuse/dev.c| 2 +-
include/linux/swap.h | 2 --
mm/shmem.c | 4 ++--
mm/swap.c| 40 +++
With the advent of fast random IO devices (SSDs, PMEM) and in-memory
swap devices such as zswap, it's possible for swap to be much faster
than filesystems, and for swapping to be preferable over thrashing
filesystem caches.
Allow setting swappiness - which defines the relative IO cost of cache
mis
Em Mon, Jun 06, 2016 at 09:31:16AM -0700, Andi Kleen escreveu:
> > [root@jouet ~]# perf stat -e
> > topdown-total-slots:u,cpu/event=topdown-total-slots/u usleep 1
> > event syntax error: 'topdown-total-slots:u,cpu/event=topdown-total-slots/u'
> > \___ parser error
> >
When (current->active_mm != mm), flush_tlb_page() does not perform a
memory barrier. In practice, this memory barrier is not needed since in
the existing call-sites the PTE is modified using atomic-operations.
This patch therefore modifies the existing smp_mb in flush_tlb_page to
smp_mb__after_atom
On Mon, 6 Jun 2016 20:55:49 +0200
Boris Brezillon wrote:
> On Mon, 6 Jun 2016 13:24:22 +0300
> Aleksei Mamlin wrote:
>
> > Add the full description of the Hynix H27UBG8T2BTR-BC NAND chip in the
> > nand_ids table so that we can later use the NAND ECC infos and ONFI timings
> > mode in controll
Noting a reference on an active file page but still deactivating it
represents a smaller cost of reclaim than noting a referenced
anonymous page and actually physically rotating it back to the head.
The file page *might* refault later on, but it's definite progress
toward freeing pages, whereas rot
tl;dr: Mutexes spin more than than rwsems which makes mutexes perform
better when contending ->i_rwsem. But, mutexes do this at the cost of
not sleeping much, even with tons of contention.
Should we do something to keep rwsem and mutex performance close to each
other? If so, should mutexes be sl
On Thu, 2016-06-02 at 17:39 +0200, Krzysztof Kozlowski wrote:
> Split out subsystem specific changes for easier reviews. This will be
> squashed with main commit.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Acked-by: Mark Salter
> arch/c6x/include/asm/dma-mapping.h | 4 ++--
> arch/c6x/kerne
This can be used by device drivers as the equivalent of of_match_device
when they are instantiated through ACPI using devicetree IDs. This is
described in Documentation/acpi/enumeration.txt
Signed-off-by: Crestez Dan Leonard
---
drivers/acpi/bus.c | 13 +++--
include/linux/acpi.h | 8
On 06/06/2016 01:18 PM, Davidlohr Bueso wrote:
Hi Ingo -- is there any reason why this series (or at least this
particular
patch) was not picked up (being in Peter's queue)? It seems that all the
recent rwsem changes are now in -tip, with the exception of these.
Thanks,
Davidlohr
Yes, I would
When devices are instatiated through devicetree the i2c_client->name is
set to the compatible string with company name stripped out. This is
then matched to the i2c_device_id table to pass the device_id to the
probe function. This id parameter is used by some device drivers to
differentiate between
Linux supports instantiating devices using devicetree ids from ACPI by setting
the id to PRP0001 and adding the devicetree compatible string in _DSD
properties. This is described in Documentation/acpi/enumeration.txt.
I've tried to use this feature using custom ACPI tables and one issue I
encounte
On Mon, 2016-06-06 at 00:18 +1000, Stephen Rothwell wrote:
> Hi Mark,
>
> Fetching the c6x tree has produced this error for the past few days:
>
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
Thanks. TI is
Nikolay Borisov writes:
> On 06/03/2016 11:41 PM, Eric W. Biederman wrote:
>> Nikolay Borisov writes:
>>
>>> On 06/02/2016 07:58 PM, Eric W. Biederman wrote:
Nikolay please see my question for you at the end.
>> [snip]
All of that said there is definitely a practical question th
The convention in these files is to use lowercase for "0x" prefixes and for
the hex constants themselves, but a few changes didn't follow that
convention, which makes the file annoying to read.
Use lowercase consistently for the hex constants. No functional change
intended.
Signed-off-by: Bjorn
On 6/6/2016 3:46 PM, Dan Williams wrote:
> On Mon, Jun 6, 2016 at 12:36 PM, Linda Knippers
> wrote:
>>
>>
>> On 6/6/2016 3:31 PM, Dan Williams wrote:
>>> On Mon, Jun 6, 2016 at 12:25 PM, Linda Knippers
>>> wrote:
On 6/4/2016 4:52 PM, Dan Williams wrote:
> There are scenarios where we
Hi,
[auto build test ERROR on cifs/for-next]
[also build test ERROR on v4.7-rc2 next-20160606]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Johannes-Weiner/mm-balance-LRU-lists-based-on
Em Mon, Jun 06, 2016 at 07:52:52PM +0900, Taeung Song escreveu:
> For example,
>
> If user config file has a wrong value 'red;default'
> instead of a normal value like 'red, default' for a key 'colors.top',
>
> # cat ~/.perfconfig
> [colors]
> medium = red;default # wrong value
>
On Mon, 6 Jun 2016 14:03:27 +1000 Stephen Rothwell
wrote:
> In file included from include/linux/crash_dump.h:5:0,
> from arch/powerpc/kernel/crash_dump.c:14:
> include/linux/kexec.h:358:9: note: previous implicit declaration of
> 'phys_to_virt' was here
> return phys_to_virt(
Em Mon, Jun 06, 2016 at 07:52:53PM +0900, Taeung Song escreveu:
> Because of die() at perf_parse_file() a config set was freed
> in collect_config(), if failed.
> But it is natural to free a config set after collect_config() is done
> when some problems happened.
>
> So, in case of failure, lastly
Commit bea7eef6949c ("ARM: dts: exynos: Fix DTC unit name warnings in
Peach Pit") fixed the DTC warnings about mismatches between unit names
and reg properties in the Exynos5420 Peach Pit DTS.
But unfortunately it also added a regression on the Peach Pit when
changing the port node names since the
Commit 5c9cbade0629 ("ARM: dts: exynos: Fix DTC unit name warnings in
Exynos5250") fixed all the DTC warnings about mismatchs between unit
names and reg properties in Exynos5250 boards DTS.
But unfortunately it also added a regression on the Exynos5250 Snow
Chromebook when changing the port node n
Hello Krzysztof,
This small series fixes the lookup for the lvds-to-eDP bridge found in
the Exynos5250 Snow and Exynos5420 Peach Pit Chromebooks. The problem
was introduced by the commits that fixed the recent DTC warnings and
it was that the OF graph logic expects the nodes to always be called
'p
Em Mon, Jun 06, 2016 at 07:52:54PM +0900, Taeung Song escreveu:
> collect_config() collect all config key-value pairs
> from config files and put each config info in config set.
> But if config set (i.e. 'set' variable at collect_config())
> is NULL, this is wrong so handle it.
Looks ok, applied.
Back in 2011, Bill Sommerfeld submitted an update to prevent ip_append_data to
create malformed packets:
Commit: d9be4f7a6f5a8da3133b832eca41c3591420b1ca
Now we're finding that we need to apply the same logic to ip_append_page to
get nfs to work with udp when UFO is enabled:
diff --git a/net/
On Sun, 5 Jun 2016 12:33:29 +0800 kbuild test robot
wrote:
> It's probably a bug fix that unveils the link errors.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 049ec1b5a76d34a6980cccdb7c0baeb4eed7a993
> commit: 888cdbc2c9a76a0e450f533b1957cd
On Mon, 6 Jun 2016 22:59:03 +0300
Aleksei Mamlin wrote:
> On Mon, 6 Jun 2016 20:55:49 +0200
> Boris Brezillon wrote:
>
> > On Mon, 6 Jun 2016 13:24:22 +0300
> > Aleksei Mamlin wrote:
> >
> > > Add the full description of the Hynix H27UBG8T2BTR-BC NAND chip in the
> > > nand_ids table so th
Hi,
[auto build test ERROR on cifs/for-next]
[also build test ERROR on v4.7-rc2 next-20160606]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Johannes-Weiner/mm-balance-LRU-lists-based-on
On Mon, Jun 6, 2016 at 1:20 PM, Linda Knippers wrote:
[..]
>> A solution to the posted-write-queue flushing needs to be available
>> and a platform can choose to use flush hints or ADR. If the NFIT
>> defines an NVDIMM device without hints we assume the platform must
>> have ADR. If the platform
Hi Alan, Geert
On Mon, Jun 6, 2016 at 11:02 AM, atull wrote:
> On Sun, 5 Jun 2016, Geert Uytterhoeven wrote:
>
>> If NO_DMA=y:
>>
>> ERROR: "bad_dma_ops" [drivers/fpga/zynq-fpga.ko] undefined!
>>
>> Add a dependency on HAS_DMA to fix this.
>>
>> Signed-off-by: Geert Uytterhoeven
>> Reviewed-
On 6/6/2016 4:31 PM, Andrew Morton wrote:
On Sun, 5 Jun 2016 12:33:29 +0800 kbuild test robot
wrote:
[...]
arch/tile/built-in.o: In function `setup_arch':
(.init.text+0x15d8): undefined reference to `early_panic'
This?
From: Andrew Morton
Subject: tile: early_printk.o is always re
On Mon, Jun 06, 2016 at 10:03:49PM +0300, Pinski, Andrew wrote:
> You may also want to look into this thread. It just got started too.
>
> -Original Message-
> From: Andrew Pinski [mailto:pins...@gmail.com]
> Sent: Monday, June 6, 2016 12:03 PM
> To: Pinski, Andrew
> Subject: Fwd: [RFC
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
g...@github.com:anholt/linux.git tags/drm-vc4-fixes-2016-06-06
for you to fetch changes up to 56d1fe0979dc9b73c1c12ee07722ac380d42a0c4:
drm/vc4: Make pageflip completion handling more robust. (2016-06-06 13:
Seeing this in next-20160606 (next-20160530 is fine), does it ring
any bells before I spend a long evening doing a bisect? The Google
doesn't seem to have seen this traceback in the past week
[ 226.9
Hi,
Am Mittwoch, 1. Juni 2016, 10:02:09 schrieb Krzysztof Kozlowski:
> My third approach for a USB power sequence which fixes usb3503+lan
> on Odroid U3 board if it was initialized by bootloader
> (e.g. for TFTP boot).
I was just tackling a similar bringup problem regarding an embedded usb hub
a
Hi,
Am Freitag, 3. Juni 2016, 10:29:20 schrieb Vincent Palatin:
> Do not shutdown the PHY if Wake-on-Lan is enabled, else it cannot wake
> us up.
>
> Signed-off-by: Vincent Palatin
> ---
> drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c | 8
> 1 file changed, 8 insertions(+)
>
> diff -
On Mon, Jun 6, 2016 at 1:00 PM, Dave Hansen wrote:
>
> I tracked this down to the differences between:
>
> rwsem_spin_on_owner() - false roughly 1% of the time
> mutex_spin_on_owner() - false roughly 0.05% of the time
>
> The optimistic rwsem and mutex code look quite similar, but
On Monday 06 June 2016 11:17 AM, Mark Brown wrote:
On Sun, Jun 05, 2016 at 07:00:21PM +0100, Sudip Mukherjee wrote:
m32r allmodconfig build is failing with the error:
ERROR: "bad_dma_ops" [sound/soc/atmel/snd-soc-atmel-pcm-pdc.ko] undefined!
The code is using DMA but the related dependency is n
On Mon, Jun 6, 2016 at 1:45 PM, Heiko Stübner wrote:
> Hi,
>
> Am Freitag, 3. Juni 2016, 10:29:20 schrieb Vincent Palatin:
>> Do not shutdown the PHY if Wake-on-Lan is enabled, else it cannot wake
>> us up.
>>
>> Signed-off-by: Vincent Palatin
>> ---
>> drivers/net/ethernet/stmicro/stmmac/dwmac-
On Mon, Jun 06, 2016 at 10:18:16AM -0700, Davidlohr Bueso wrote:
> Hi Ingo -- is there any reason why this series (or at least this particular
> patch) was not picked up (being in Peter's queue)? It seems that all the
> recent rwsem changes are now in -tip, with the exception of these.
I placed it
On Mon, Jun 06, 2016 at 07:52:00PM +, Mathieu Desnoyers wrote:
> - On May 30, 2016, at 9:18 AM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
> Adding Ingo and Peter in CC, considering that it touches to tracing and
> the scheduler.
> >> +/*
> >> + * Tracepoint for showing pr
From: Lucas Stach
This fixes cross compilation of libapi.
Signed-off-by: Lucas Stach
Cc: Jiri Olsa
Cc: ker...@pengutronix.de
Cc: patchwork-...@pengutronix.de
Link:
http://lkml.kernel.org/r/1458235670-27341-1-git-send-email-l.st...@pengutronix.de
Signed-off-by: Arnaldo Carvalho de Melo
---
t
This attribute was added 3 years ago by
commit 3eacf866559c ("brcmfmac: introduce brcmf_cfg80211_vif structure")
but it remains unused since then. It seems we can safely drop it.
Signed-off-by: Rafał Miłecki
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 9 +++--
drivers/n
From: He Kuang
There's a display inconsistency when there are multiple tracepoint
events, some of which have the 'call-graph' config option set but the
first one hasn't, i.e. the whole logic for call graph processing is
enabled only if the first tracepoint event has call-graph set.
For instance,
From: Andi Kleen
When --metric-only is enabled there were no headers for the topology in
interval mode. Also when headers were printed they were on a separate
line.
Before:
$ perf stat --metric-only -A -I 1000 -a
1.001038376 frontend cycles idle insn per cycle stalled cycles per
://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-20160606
for you to fetch changes up to 7db91f251056f90fec4121f028680ab3153a0f3c:
perf config: Handle the error when config set is NULL at collect_config()
(2016-06-06 17:43:19 -0300
From: Taeung Song
collect_config() collect all config key-value pairs from config files
and put each config info in config set. But if config set (i.e. 'set'
variable at collect_config()) is NULL, this is wrong so handle it.
Signed-off-by: Taeung Song
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc:
From: Arnaldo Carvalho de Melo
Out of perf_evsel__intval(), that requires passing the variable name,
that will then be searched in the list of tracepoint variables for the
given evsel.
In cases such as syscall file descriptor ("fd") tracking, this is
wasteful, we need just to use perf_evsel__fie
From: Wang Nan
If zalloc fail, setting evlist->mmap[i].fd is unsafe and
perf_evlist__alloc_mmap() should bail out right after that.
Signed-off-by: Wang Nan
Acked-by: Masami Hiramatsu
Cc: He Kuang
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Zefan Li
Cc: pi3or...@163.com
Fixes: d4c6fb36ac2c ("perf ev
From: Andi Kleen
'perf test' tries to parse all entries in /sys/devices/cpu/events/.
Ignore the special entries like '.scale', which cannot be directly
parsed as an event. This patch assumes all files containing a '.' are
special and can be ignored.
Reported-by: Arnaldo Carvalho de Melo
Signed-
From: Andi Kleen
Add basic plumbing for TopDown in perf stat
TopDown is intended to replace the frontend cycles idle/ backend cycles
idle metrics in standard perf stat output. These metrics are not
reliable in many workloads, due to out of order effects.
This implements a new --topdown mode in
On 06/06/16 09:40, Peter Zijlstra wrote:
> On Mon, Jun 06, 2016 at 03:59:06PM +, Chen, Yu C wrote:
>
+ if (hibernation_in_resume())
+ mwait_ptr = empty_zero_page;
+ else
+ mwait_ptr = ¤t_thread_info()->flags;
>>>
>>> Why is this conditional? Is there any
From: Taeung Song
If a config file has wrong key-value pairs, the perf process will be
forcibly terminated by die() at perf_parse_file() called by
perf_config() so terminal settings can be crushed because of unusual
termination.
For example:
If user config file has a wrong value 'red;default' i
On Mon, 6 Jun 2016 22:31:38 +0200
Boris Brezillon wrote:
> On Mon, 6 Jun 2016 22:59:03 +0300
> Aleksei Mamlin wrote:
>
> > On Mon, 6 Jun 2016 20:55:49 +0200
> > Boris Brezillon wrote:
> >
> > > On Mon, 6 Jun 2016 13:24:22 +0300
> > > Aleksei Mamlin wrote:
> > >
> > > > Add the full descr
From: Andi Kleen
When in CSV mode --metric-only outputs an header, unlike the other
modes. Previously it did not properly print headers for the aggregation
columns, so the headers were actually shifted against the real values.
Fix this here by outputting the correct headers for CSV.
v2: Indent
On Fri, Jun 3, 2016 at 3:35 PM, Viresh Kumar wrote:
> Hi Rafael,
>
> So all my patches are contained in two series. The first one is:
>
> [PATCH V3 0/8] cpufreq: cleanups and reorganization
>
> which I have sent this morning. It does some cleanup and shall be
> applied regardless of this series.
>
From: Andi Kleen
Implement the TopDown formulas in 'perf stat'. The topdown basic metrics
reported by the kernel are collected, and the formulas are computed and
output as normal metrics.
See the kernel commit exporting the events for details on the used
metrics.
Committer note:
Output example
On 06/06/2016 04:46 PM, Linus Torvalds wrote:
On Mon, Jun 6, 2016 at 1:00 PM, Dave Hansen wrote:
I tracked this down to the differences between:
rwsem_spin_on_owner() - false roughly 1% of the time
mutex_spin_on_owner() - false roughly 0.05% of the time
The optimistic rwsem
On Wed, Jun 1, 2016 at 9:10 AM, Christian König wrote:
> From: Christian König
>
> vm_flush() now comes directly after vm_grab_id().
>
> Signed-off-by: Christian König
For the series:
Acked-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu.h| 1 -
> drivers/gpu/drm/amd/amdgpu/a
On 6/6/2016 4:36 PM, Dan Williams wrote:
> On Mon, Jun 6, 2016 at 1:20 PM, Linda Knippers wrote:
> [..]
>>> A solution to the posted-write-queue flushing needs to be available
>>> and a platform can choose to use flush hints or ADR. If the NFIT
>>> defines an NVDIMM device without hints we assu
prot_sg_cnt has been assigned with the value of ret which we have
already checked to be non-zero so prot_sg_cnt can never be zero at this
point of the code and hence the else part can never execute.
And since we know prot_sg_cnt is non zero there is no use for the
if condition also.
Signed-off-by:
On Mon, Jun 06, 2016 at 01:46:23PM -0700, Linus Torvalds wrote:
> So my gut feel is that we do want to have the same heuristics for
> rwsems and mutexes (well, modulo possible actual semantic differences
> due to the whole shared-vs-exclusive issues).
>
> And I also suspect that the mutexes have
On Mon, Jun 6, 2016 at 2:13 PM, Waiman Long wrote:
>
> The tricky part about optimistic spinning in rwsem is that we don't know for
> sure if any of the lock holding readers is running or not.
I'm notm sure how common the reader-vs-writer contention is, at least
for the new inode use. I'm sure yo
This patch set adds some needed preparations for the upcoming NVMe over
Fabrics support.
Contains:
- Allow transfer size limitations for NVMe transports
- Add the get_log_page command definition required by the NVMe target
- more helpers in core code that can be used by various transports
- add so
Reviewed-by: Jay Freyensee
Reviewed-by: Sagi Grimberg
Reviewed-by: Ming Lin
Signed-off-by: Christoph Hellwig
---
include/linux/nvme.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index 9807d98..a9b8c7b 100644
--- a/include/linux/nvme.h
+
From: Armen Baloyan
Add get_log_page command structure and a corresponding entry in
nvme_command union
Signed-off-by: Armen Baloyan
Reviewed-by: Jay Freyensee
Reviewed--by: Sagi Grimberg
Signed-off-by: Christoph Hellwig
---
include/linux/nvme.h | 19 +++
1 file changed, 19 i
These have been added in NVMe 1.2 and we'll need at least oaes for the
NVMe target driver.
Reviewed-by: Sagi Grimberg
Reviewed-by: Jay Freyensee
Signed-off-by: Christoph Hellwig
---
include/linux/nvme.h | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/nvme.
Some transport drivers may have a lower transfer size than
the controller. So allow the transport to set it in the
controller max_hw_sectors.
Reviewed-by: Sagi Grimberg
Signed-off-by: Christoph Hellwig
---
drivers/nvme/host/core.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
di
This patch set adds the necessary infrastructure for the NVMe over
Fabrics functionality and the NVMe over Fabrics library itself.
First we add some needed parameters to NVMe request allocation such as flags
(for reserved commands - connect and keep-alive), also support tag
allocation of a given q
We want to apply this to Fabrics drivers as well, so move it to common
code.
Reviewed-by: Jay Freyensee
Reviewed-by: Sagi Grimberg
Tested-by: Ming Lin
Signed-off-by: Christoph Hellwig
---
drivers/nvme/host/core.c | 17 ++---
drivers/nvme/host/pci.c | 10 +-
2 files change
From: Ming Lin
So it can be used by fabrics driver as well.
Signed-off-by: Ming Lin
Reviewed-by: Sagi Grimberg
Signed-off-by: Christoph Hellwig
---
drivers/nvme/host/core.c | 17 +
drivers/nvme/host/nvme.h | 1 +
drivers/nvme/host/pci.c | 16
3 files change
- delete_controller: This attribute allows to delete a controller.
A driver is not obligated to support it (pci doesn't) so it is
created only if the driver supports it. The new fabrics drivers
will support it (essentialy a disconnect operation).
Usage:
echo > /sys/class/nvme/nvme0/delet
From: Ming Lin
Pass in nvme_ctrl, so it can be used by the fabrics drivers also.
Also update to upstream version and rename it to nvme_cancel_request.
Signed-off-by: Ming Lin
Signed-off-by: Sagi Grimberg
Signed-off-by: Christoph Hellwig
---
drivers/nvme/host/pci.c | 9 +
1 file chang
From: Ming Lin
For some protocols like NVMe over Fabrics we need to be able to send
initialization commands to a specific queue.
Based on an earlier patch from Christoph Hellwig .
Signed-off-by: Ming Lin
Signed-off-by: Christoph Hellwig
---
block/blk-mq.c | 33 +++
The NVMe over Fabrics specification defines a protocol interface and
related extensions to NVMe that enable operation over network protocols.
The NVMe over Fabrics specification has an NVMe Transport binding for
each NVMe Transport.
This patch adds the fabrics related definitions:
- fabric specifi
This patch set adds a generic NVMe over Fabrics target. The
implementation conforms to the NVMe 1.2b specification (which
includes Fabrics) and provides the NVMe over Fabrics access
to Linux block devices.
The target implementation consists of several elements:
- NVMe target core: defines and man
This patch implements the RDMA transport for the NVMe over Fabrics target,
which allows exporting NVMe over Fabrics functionality over RDMA fabrics
(Infiniband, RoCE, iWARP).
All NVMe logic is in the generic target and this module just provides a
small glue between it and the generic code in the R
From: Sagi Grimberg
The new nvme-rdma driver will need to reinitialize all the tags as part of
the error recovery procedure (realloc the tag memory region). Add a helper
in blk-mq for it that can iterate over all requests in a tagset to make
this easier.
Signed-off-by: Sagi Grimberg
Tested-by:
The only caller of get_gadget_descs() has already dereferenced udc
before calling this function, so udc can not be NULL at this point of
the code and hence no use of checking it.
Signed-off-by: Sudip Mukherjee
---
drivers/usb/usbip/vudc_sysfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
This patch implements adds nvme-loop which allows to access local devices
exported as NVMe over Fabrics namespaces. This module can be useful for
easy evaluation, testing and also feature experimentation.
To createa nvme-loop device you need to configure the NVMe target to
export a loop port (see
Periodic keep-alive is a mandatory feature in NVMe over Fabrics, and
optional in NVMe 1.2.1 for PCIe. This patch adds periodic keep-alive
sent from the host to verify that the controller is still responsive
and vice-versa. The keep-alive timeout is user-defined (with
keep_alive_tmo connection par
This patch implements the RDMA host (initiator in SCSI speak) driver. It
can be used to connect to remote NVMe over Fabrics controllers over
Infiniband, RoCE or iWarp, and uses the existing NVMe core driver as well
a the new fabrics library.
To connect to all NVMe over Fabrics controller reachabl
From: Sagi Grimberg
The new NVMe over fabrics target will make use of this outside from a
module.
Signed-off-by: Sagi Grimberg
Signed-off-by: Christoph Hellwig
---
block/blk-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/blk-core.c b/block/blk-core.c
index 2475b1c7..ad5270e
This patch introduces a implementation of NVMe subsystems,
controllers and discovery service which allows to export
NVMe namespaces across fabrics such as Ethernet, FC etc.
The implementation conforms to the NVMe 1.2.1 specification
and interoperates with NVMe over fabrics host implementations.
C
From: Sagi Grimberg
KAS: keep-alive support and granularity of kato in units of 100 ms
nvme_admin_keep_alive opcode: 0x18
Signed-off-by: Sagi Grimberg
Signed-off-by: Christoph Hellwig
---
include/linux/nvme.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/include/lin
From: Sagi Grimberg
NVMe over Fabrics RDMA transport defines a connection establishment
protocol over the RDMA connection manager. This header will be used by
both the host and target drivers to negotiate the connection
establishment parameters.
Signed-off-by: Jay Freyensee
Signed-off-by: Ming
101 - 200 of 1112 matches
Mail list logo