Re: [PATCH 2/3] media: vim2m: use per-file handler work queue

2019-01-30 Thread Ezequiel Garcia
On Tue, 2019-01-29 at 14:00 -0200, Mauro Carvalho Chehab wrote: > It doesn't make sense to have a per-device work queue, as the > scheduler should be called per file handler. Having a single > one causes failures if multiple streams are filtered by vim2m. > Having a per-device workqueue should em

Re: [PATCH v3 0/3] update infiniband uverbs documentation

2019-01-30 Thread Joel Nider
Hi Jon, Have you had a chance to review this patchset? Thanks, Joel Nider/Haifa/IBM@IBMIL wrote on 01/22/2019 12:00:32 PM: > From: Joel Nider/Haifa/IBM@IBMIL > To: "Jonathan Corbet" > Cc: "Jason Gunthorpe" , "Leon Romanovsky" , > "Doug Ledford" , "Mike Rapoport" , > Joel Nider/Haifa/IBM@IB

Re: [PATCH 2/3] media: vim2m: use per-file handler work queue

2019-01-30 Thread Mauro Carvalho Chehab
Em Wed, 30 Jan 2019 09:41:44 -0300 Ezequiel Garcia escreveu: > On Tue, 2019-01-29 at 14:00 -0200, Mauro Carvalho Chehab wrote: > > It doesn't make sense to have a per-device work queue, as the > > scheduler should be called per file handler. Having a single > > one causes failures if multiple str

Re: [PATCH 2/3] media: vim2m: use per-file handler work queue

2019-01-30 Thread Ezequiel Garcia
Hey Mauro, On Wed, 2019-01-30 at 11:19 -0200, Mauro Carvalho Chehab wrote: > Em Wed, 30 Jan 2019 09:41:44 -0300 > Ezequiel Garcia escreveu: > > > On Tue, 2019-01-29 at 14:00 -0200, Mauro Carvalho Chehab wrote: > > > It doesn't make sense to have a per-device work queue, as the > > > scheduler sh

Re: [PATCH] rcu docs: repair some whitespace damage

2019-01-30 Thread Paul E. McKenney
On Tue, Jan 29, 2019 at 03:05:46PM -0700, Tycho Andersen wrote: > While reading the docs I noticed some whitespace damage in diagram. Let's > fix it up to be consistent with elsewhere in the document: use one leading > tab, followed by spaces for any additional whitespace required. > > Signed-off-

Re: [RFC v7 2/5] dt-bindings: pstore-block: new support for blkoops

2019-01-30 Thread Rob Herring
On Wed, Jan 23, 2019 at 08:05:13PM +0800, liaoweixiong wrote: > Create DT binding document for blkoops. > > Signed-off-by: liaoweixiong > --- > .../devicetree/bindings/pstore-block/blkoops.txt | 32 > ++ /bindings/pstore/... I wouldn't call it blkoops either. I believe ra

[PATCH resend 1/3] hwmon: (lm85) remove freq_map size hardcodes

2019-01-30 Thread Jeremy Gebben
Allow support for chips that support more than 8 frequencies. The size still must be a power of two. Signed-off-by: Jeremy Gebben --- drivers/hwmon/lm85.c | 25 +++-- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/drivers/hwmon/lm85.c b/drivers/hwmon/lm85.c

[PATCH resend 2/3] hwmon: (lm85) Document the LM96000 as supported

2019-01-30 Thread Jeremy Gebben
It has been supported as a generic lm85 for quite some time. Signed-off-by: Jeremy Gebben --- Documentation/hwmon/lm85 | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Documentation/hwmon/lm85 b/Documentation/hwmon/lm85 index 7c49feaa79d2..9f3a945d1b80 100644 --- a/Docume

[PATCH resend 3/3] hwmon: (lm85) add support for LM96000 high frequencies

2019-01-30 Thread Jeremy Gebben
This chip expands the freqency field from 3 to 4 bits, to add more frequencies in the 22.5 to 30 kHz ranges. Signed-off-by: Jeremy Gebben --- Documentation/hwmon/lm85 | 3 +++ drivers/hwmon/lm85.c | 9 + 2 files changed, 12 insertions(+) diff --git a/Documentation/hwmon/lm85 b/Docum

Re: [RESEND PATCH v4 0/3] fs/dcache: Track # of negative dentries

2019-01-30 Thread Waiman Long
On 01/15/2019 04:27 PM, Waiman Long wrote: > On 12/16/2018 02:37 PM, Linus Torvalds wrote: >> On Fri, Dec 14, 2018 at 1:53 PM Waiman Long wrote: >>> This patchset addresses 2 issues found in the dentry code and adds a >>> new nr_dentry_negative per-cpu counter to track the total number of >>> nega

Re: [PATCH resend 1/3] hwmon: (lm85) remove freq_map size hardcodes

2019-01-30 Thread Guenter Roeck
On Wed, Jan 30, 2019 at 09:14:45AM -0700, Jeremy Gebben wrote: > > Allow support for chips that support more than 8 frequencies. > The size still must be a power of two. > This is risky. Someone later may not know/remember and expand the table without maintaining that restriction. I would sugges

[PATCH v2] doc: Change LXR references to elixir.bootlin.com

2019-01-30 Thread Jonathan Neuschäfer
Recently, Free Electrons was renamed to Bootlin[1]. Less recently, the Linux Cross Reference (LXR) at lxr.free-electrons.com was replaced by Elixir[2], and lxr.free-electrons.com redirected first to elixir.free-electrons.com and now to elixir.bootlin.com. [1]: https://bootlin.com/blog/free-electro

Re: [PATCH 2/3] media: vim2m: use per-file handler work queue

2019-01-30 Thread Mauro Carvalho Chehab
Em Wed, 30 Jan 2019 11:56:58 -0300 Ezequiel Garcia escreveu: > Hey Mauro, > > On Wed, 2019-01-30 at 11:19 -0200, Mauro Carvalho Chehab wrote: > > Em Wed, 30 Jan 2019 09:41:44 -0300 > > Ezequiel Garcia escreveu: > > > > > On Tue, 2019-01-29 at 14:00 -0200, Mauro Carvalho Chehab wrote: > > >

Re: [PATCH v4 01/12] Documentation: Document arm64 kpti control

2019-01-30 Thread Andre Przywara
On Fri, 25 Jan 2019 12:07:00 -0600 Jeremy Linton wrote: Hi, > For a while Arm64 has been capable of force enabling > or disabling the kpti mitigations. Lets make sure the > documentation reflects that. > > Signed-off-by: Jeremy Linton > Cc: Jonathan Corbet > Cc: linux-doc@vger.kernel.org > --

Re: [PATCH v4 02/12] arm64: Provide a command line to disable spectre_v2 mitigation

2019-01-30 Thread Andre Przywara
On Fri, 25 Jan 2019 12:07:01 -0600 Jeremy Linton wrote: Hi, > There are various reasons, including bencmarking, to disable spectrev2 > mitigation on a machine. Provide a command-line to do so. > > Signed-off-by: Jeremy Linton > Cc: Jonathan Corbet > Cc: linux-doc@vger.kernel.org Reviewed-by:

Re: [PATCH v2] doc: Change LXR references to elixir.bootlin.com

2019-01-30 Thread Martin Kepplinger
 Martin Kepplinger | Entwicklung Software  GINZINGER ELECTRONIC SYSTEMS GMBH Tel.: +43 7723 5422 157 Mail: martin.kepplin...@ginzinger.com Web: www.ginzinger.com On 30.01.19 18:25, Jonathan Neuschäfer wrote: Recently, Free Electrons was renamed to Bootlin[1]. Less recently, the Linux Cros

Re: [RESEND PATCH v4 0/3] fs/dcache: Track # of negative dentries

2019-01-30 Thread Linus Torvalds
On Wed, Jan 30, 2019 at 8:40 AM Waiman Long wrote: > > Ping. Will this patch be picked up? Can you re-send the patch-set and I'll just apply it directly since it seems to be languishing otherwise. Linus

Re: [RESEND PATCH v4 0/3] fs/dcache: Track # of negative dentries

2019-01-30 Thread Waiman Long
On 01/30/2019 01:35 PM, Linus Torvalds wrote: > On Wed, Jan 30, 2019 at 8:40 AM Waiman Long wrote: >> Ping. Will this patch be picked up? > Can you re-send the patch-set and I'll just apply it directly since it > seems to be languishing otherwise. > > Linus Sure. Thanks for your

[RESEND PATCH v4 3/3] fs/dcache: Track & report number of negative dentries

2019-01-30 Thread Waiman Long
The current dentry number tracking code doesn't distinguish between positive & negative dentries. It just reports the total number of dentries in the LRU lists. As excessive number of negative dentries can have an impact on system performance, it will be wise to track the number of positive and ne

[RESEND PATCH v4 1/3] fs/dcache: Fix incorrect nr_dentry_unused accounting in shrink_dcache_sb()

2019-01-30 Thread Waiman Long
The nr_dentry_unused per-cpu counter tracks dentries in both the LRU lists and the shrink lists where the DCACHE_LRU_LIST bit is set. The shrink_dcache_sb() function moves dentries from the LRU list to a shrink list and subtracts the dentry count from nr_dentry_unused. This is incorrect as the nr_d

[RESEND PATCH v4 2/3] fs: Don't need to put list_lru into its own cacheline

2019-01-30 Thread Waiman Long
The list_lru structure is essentially just a pointer to a table of per-node LRU lists. Even if CONFIG_MEMCG_KMEM is defined, the list field is just used for LRU list registration and shrinker_id is set at initialization. Those fields won't need to be touched that often. So there is no point to mak

[RESEND PATCH v4 0/3] fs/dcache: Track # of negative dentries

2019-01-30 Thread Waiman Long
v3->v4: - Drop patch 4 as it is just a minor optimization. - Add a cc:stable tag to patch 1. - Clean up some comments in patch 3. v2->v3: - With confirmation that the dummy array in dentry_stat structure was never a replacement of a previously used field, patch 3 is now reverted

Re: [PATCH v3 0/3] update infiniband uverbs documentation

2019-01-30 Thread Jonathan Corbet
On Wed, 30 Jan 2019 14:57:21 +0200 "Joel Nider" wrote: > Have you had a chance to review this patchset? I've been mostly away from the keyboard for the last week; will be back and dealing with things soon. Thanks, jon

Re: [PATCH v2] doc: Change LXR references to elixir.bootlin.com

2019-01-30 Thread Federico Vaga
On 2019-01-30 18:25, Jonathan Neuschäfer wrote: Recently, Free Electrons was renamed to Bootlin[1]. Less recently, the Linux Cross Reference (LXR) at lxr.free-electrons.com was replaced by Elixir[2], and lxr.free-electrons.com redirected first to elixir.free-electrons.com and now to elixir.bootli

docs tree

2019-01-30 Thread Tobin C. Harding
Hi Jon, Has the docs tree moved? I haven't fetched it lately and this morning I get: $ git fetch corbet fatal: unable to connect to git3.lwn.net: git3.lwn.net[0: 45.79.184.34]: errno=Connection refused All my other trees fetch ok. Relevant .git/config entry is:

Re: docs tree

2019-01-30 Thread Randy Dunlap
On 1/30/19 5:25 PM, Tobin C. Harding wrote: > Hi Jon, > > Has the docs tree moved? I haven't fetched it lately and this morning I > get: > > $ git fetch corbet > fatal: unable to connect to git3.lwn.net: > git3.lwn.net[0: 45.79.184.34]: errno=Connection refused > > All my othe

Re: docs tree

2019-01-30 Thread Tobin C. Harding
On Thu, Jan 31, 2019, at 12:37, Randy Dunlap wrote: > On 1/30/19 5:25 PM, Tobin C. Harding wrote: > > Hi Jon, > > > > Has the docs tree moved? I haven't fetched it lately and this morning I > > get: > > > > $ git fetch corbet > > fatal: unable to connect to git3.lwn.net: > > git3.lwn

[PATCH v3 0/5] Optimize writecache when using pmem as cache

2019-01-30 Thread Huaisheng Ye
From: Huaisheng Ye This patch set could be used for dm-writecache when use persistent memory as cache data device. Patch 1 and 2 go towards removing unused parameter and codes which actually doesn't really work. Patch 3 and 4 are targeted at solving problem fn ctr failed to work due to invalid

[PATCH v3 3/5] dm-writecache: expand pmem_reinit for struct dm_writecache

2019-01-30 Thread Huaisheng Ye
From: Huaisheng Ye When use persistent memory as cache data device, sometimes the super block of pmem has messy data stored in it. That would have risk to lead fn ctr failed to work due to invalid magic or version. Here we expand pmem_reinit to optional parameters in order to solve this issue. W

[PATCH v3 1/5] dm-writecache: remove unused size to writecache_flush_region

2019-01-30 Thread Huaisheng Ye
From: Huaisheng Ye writecache_flush_region doesn't use size to calculate flush region. That uses _set_bits to mark the region in dirty_bitmap directly. Signed-off-by: Huaisheng Ye --- drivers/md/dm-writecache.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/dr

[PATCH v3 2/5] dm-writecache: get rid of memory_data flush to writecache_flush_entry

2019-01-30 Thread Huaisheng Ye
From: Huaisheng Ye writecache_flush_region only works when SSD mode. If wc->pmem_mode sets, writecache_flush_region doesn't need to be called in writecache_flush_entry. Signed-off-by: Huaisheng Ye --- drivers/md/dm-writecache.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/md/dm

[PATCH v3 4/5] Documentation/device-mapper: add optional parameter reinit

2019-01-30 Thread Huaisheng Ye
From: Huaisheng Ye Add intro and usage guide for reinit. Signed-off-by: Huaisheng Ye --- Documentation/device-mapper/writecache.txt | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/device-mapper/writecache.txt b/Documentation/device-mapper/writecache.txt index 01532b3..25

[PATCH v3 5/5] dm-writecache: output seq_count within status

2019-01-30 Thread Huaisheng Ye
From: Huaisheng Ye seq_count is important for flush operations, output it within status for debugging and analyzing code behavior. Signed-off-by: Huaisheng Ye --- drivers/md/dm-writecache.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/md/dm-writecache.c b/dri

wohltätige Spende von 2.800.000 euro

2019-01-30 Thread ''Friedrich mayhofer''
Mein Name ist Friedrich Mayrhofer, meine Frau und ich haben im Dezember 2015 eine Jackpot-Lotterie in Höhe von 50 Millionen Dollar gewonnen. Wir spenden die Summe von 2.800.000 Millionen Euro an 5 glückliche Personen, von denen Sie einer der Begünstigten sind. und wir spenden 2.800.000,00 an Sie

[PATCH 1/3] docs: Fix SLUB docs typo

2019-01-30 Thread Tobin C. Harding
From: "Tobin C. Harding" There is a minor typo in SLUB documentation. Fix typo. Signed-off-by: Tobin C. Harding --- Documentation/vm/slub.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/vm/slub.rst b/Documentation/vm/slub.rst index 195928808..0871c5849 10

[PATCH 0/3] docs: vm: Fix typo and build warnings

2019-01-30 Thread Tobin C. Harding
From: "Tobin C. Harding" Hi Jon, This patchset started as a spelling typo fix to the SLUB docs, while doing this I noticed a few build warnings for vm/ so build warning fixes make up the rest of the set. Patch 3 uses an underscore instead of a hyphen in the label name. This clears the warning

[PATCH 2/3] docs: Add missing colon

2019-01-30 Thread Tobin C. Harding
From: "Tobin C. Harding" sphinx emits warning WARNING: Inline emphasis start-string without end-string. This is caused by a missing colon. Add missing colon, clearing shpinx build warning. Signed-off-by: Tobin C. Harding --- Documentation/vm/slub.rst | 2 +- 1 file changed, 1 inserti

[PATCH 3/3] docs: Use underscore not hyphen in label

2019-01-30 Thread Tobin C. Harding
From: "Tobin C. Harding" sphinx emits warning WARNING: undefined label: memory-allocation ... This seems to be caused by the use of a hyphen in the label name instead of an underscore. Using an underscore for the label name and the reference clears the warning. Use underscore not hyphe