bly correct ::-)
The patch is below, the scripts are attached, and everything is
available here:
http://lug.udel.edu/~ross/git/
Now to see what I come up with for commit, push, and pull...
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematicians, and all those wh
stuff, since it looks like there's superior
work. Looks cool!
I must say, the git as a filesystem thing is really neat. This has
been one of the more fun projects I've toyed around with.
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematician
annot initialize the agpgart module.
DRM: Fill_in_dev failed.
Thanks very much for any tips!
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematicians, and all those who
make empty prophecies. The danger already exists that the mathematicians
have made a covenant with
On Sat, Apr 16, 2005 at 06:47:13PM +1000, Dave Airlie wrote:
> You didn't load the agp chipset module..
> it would be nice if it happened automatically...
Spot on - thanks man. Will update rc scripts from 2.4. Thanks!
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian
a result, I mostly
use OSS emulation for non-music related things - Frank Barknecht has
info at http://alsa.opensrc.org/index.php?page=DmixPlugin on setting
this up. Runing all my audio through that fixes the problem, since it
just resample everything to the running rate.
--
Ross Vandegrift
[EMAI
nly use ReiserFS
and have a few reasonably sized projects in Ardour that work fine:
maybe 20 tracks, with 10-15 plugins (in the whole project), and I can
do overdubs with no problems. It may be relevant that I only have a
four track card and so load is too small.
But at least in my practice, it has
On 02/19/2013 05:45 PM, Greg Kroah-Hartman wrote:
When vt.init_hide is set, suppress output on newly created consoles
until an affirmative switched to that console. This prevents boot
output from displaying (and clobbering splash screens, etc...)
without disabling the console entirely.
What's
On 02/19/2013 08:45 PM, Greg Kroah-Hartman wrote:
> On Tue, Feb 19, 2013 at 08:04:05PM -0800, Andy Ross wrote:
> > There's a (sort of) similar commonly-used option, vga=current, which
> > prevents a mode switch for the special case of VGA/vesa. But that
> > doesn&#
When vt.init_hide is set, suppress output on newly created consoles
until an affirmative switch to that console. This prevents boot
output from displaying (and clobbering splash screens, etc...) without
disabling the console entirely.
Signed-off-by: Andy Ross
Signed-off-by: Kirill A. Shutemov
On 02/20/2013 12:57 PM, Pavel Machek wrote:
I'm sure something creative can be done with fake init that shuts
the console up then execs previous init. No need to add more kernel
knobs, I'd say.
Fair enough, but some last words:
That's argument is the "it's about logging" hypothesis again. Eve
I know I said the last words were my last, but this message and
Pavel's gave me some vain hope that I might be able to win this one on
the merits, so I'm trying again just to make the situation clear:
On 02/20/2013 05:12 PM, Greg Kroah-Hartman wrote:
I don't see why this is even needed for surfa
On Fri, Feb 08, 2008 at 01:07:46PM +0100, Andi Kleen wrote:
> On Thu, Feb 07, 2008 at 02:44:46PM -0500, Ross Vandegrift wrote:
> > On Wed, Feb 06, 2008 at 09:53:57AM +0100, Andi Kleen wrote:
> > My initial test is end-to-end 1000Mbps, but I've got a few different
> > p
unused devices:
# cat /proc/sys/dev/raid/speed_limit_min
1
MD is unable to reach its minimum rebuild rate while other system
activity is ongoing. You might want to lower this number to see if that
gets you out of the stalls.
Or temporarily shut down mythtv.
I will try lowering those
On 07/25/2012 10:00 PM, Kevin Ross wrote:
unused devices:
# cat /proc/sys/dev/raid/speed_limit_min
1
MD is unable to reach its minimum rebuild rate while other system
activity is ongoing. You might want to lower this number to see if
that
gets you out of the stalls.
Or temporarily
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel (3.4.6 right now).
As far as I can see, the latest 3.2 stable does not contain the delayed
stripe fix.
And I was looking at the wrong version; 3
On 07/26/2012 07:27 PM, David Dillow wrote:
On Thu, 2012-07-26 at 19:17 -0700, Kevin Ross wrote:
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel (3.4.6 right now).
As far as I can see, the
On 07/26/2012 07:53 PM, Kevin Ross wrote:
On 07/26/2012 07:27 PM, David Dillow wrote:
On Thu, 2012-07-26 at 19:17 -0700, Kevin Ross wrote:
On 07/26/2012 07:17 PM, David Dillow wrote:
On Thu, 2012-07-26 at 22:15 -0400, David Dillow wrote:
If you can, upgrade to the latest 3.4 stable kernel
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of "job one" on older kernels.
I have not, thanks for the tip, I'll look into that now.
Thanks!
-- Kevin
--
To unsubscribe from this list: send the line "unsubscri
On 07/27/2012 09:45 PM, Grant Coady wrote:
On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of "job one" on older kernels.
I have not, thanks for the tip, I'll look i
though it names the directory pointed to by the
symbolic link.
So while Linux gives ENOTDIR for "rmdir X/", the others remove Y.
Is this a bug? If it is, I can have a go at writing a patch.
Regards
--
Ross Lagerwall
--
To unsubscribe from this list: send the line "unsubsc
Hi,
Ever since commit 421b40a6286e ("tty/vt: Fix vc_deallocate() lock
order"), the first VT does not clear when I log out. AFAIK, this means
that disallocation is not working? The problem only affects the first
VT, the others clear when logging out.
Regards
--
Ross Lagerwall
--
To u
Commit 421b40a6286e ("tty/vt: Fix vc_deallocate() lock order") changed
the behavior when deallocating VT 1. Previously if trying to
deallocate VT1 and it is busy, we would return EBUSY. The commit
changed this to return 0 (success).
This commit restores the old behavior.
Signed-of
guest
interoperate with qemu etc. On bare metal it will be much more opaque
and ugly; the processor related AML will probably burrow down into an
SMI to do the real work.
Ross
>
> All I'm saying is, let's not hurry too much before we actually can
> really trigger this on baremetal
vice, most
of the connections are short-lived connections for small pieces of data -
so I'm not really convinced that window scaling and selective ACK are all
that important.
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematicians, and all those who
mak
that have been left
on compromised systems, so it wouldn't be too difficult to get some
numbers.
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematicians, and all those who
make empty prophecies. The danger already exists that the mathematicians
have made a
sten+0x4a/0x66
[] sys_socketcall+0x98/0x19e
[] do_syscall_trace+0xab/0xb1
[] syscall_call+0x7/0xb
===
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematicians, and all those who
make empty prophecies. The danger already exists that the m
Hello,
I'm having a problem. After a while, my software RAID rebuild becomes
extremely slow, and the filesystem on the RAID is essentially blocked.
I don't know what is causing this. I guess it could be a bad drive, but
how can I find out?
I used atop to show the transfer speeds to each d
Thank you very much for taking the time to look into this.
On 07/25/2012 06:00 PM, Phil Turmel wrote:
Piles of small reads scattered across multiple drives, and a
concentration of queued writes to /dev/sda. What's on /dev/sda?
It's not a member of the raid, so it must be some other system task
On 07/25/2012 07:09 PM, CoolCold wrote:
You might be interested in write intent bitmap then, it gonna help a
lot. (resending in plain text)
Thanks, I'll look into that!
-- Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vg
The USB TrackPoint name string contains a space at the trailing end that
can cause confusion/difficulty when creating udev rules. Example:
"Synaptics Inc. Composite TouchPad / TrackPoint (Stick) "
This patch removes the trailing space.
Signed-off-by: Bob Ross
---
This patch was
to
choose the mode at runtime.
Ross
diff -ur linux-2.6.11/drivers/pci/Kconfig linux-2.6.11-new/drivers/pci/Kconfig
--- linux-2.6.11/drivers/pci/Kconfig2005-03-01 23:37:51.0 -0800
+++ linux-2.6.11-new/drivers/pci/Kconfig2005-04-01 07:19:32.0
-0800
ammar comments noted ]
One thing I did fail to mention in my original post is that all of this
could be done by rc scripts from user space, but that seems unclean to me.
Ross
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
on is to keep it as a config option and add a
CONFIG_OBSCURE so that most people don't ever see option, but the few
that need to can.
Ross
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info a
the exact same
hardware. A setting of =y will screw user A and a setting of =n will
screw user B. Ideally, they would both get better hardware, but that
is not always an option.
Ross
Ross
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
Hi Richard,
Richard Drummond escreveu:
Attached is a patch against 2.6.11.7 which tidies up the tdfxfb framebuffer
size detection code a little and fixes the broken support for Voodoo4/5 cards.
(I haven't tested this on a Voodoo5, however, because I don't have the
hardware).
I /do/ have the hard
On 8/26/05, Hugh Dickins <[EMAIL PROTECTED]> wrote:
> On Fri, 26 Aug 2005, Ross Biro wrote:
> > On 8/26/05, Hugh Dickins <[EMAIL PROTECTED]> wrote:
> > >
> > > The refaulting will hurt the performance of something: let's
> > > just hope
;m suggesting that we change the code to do the same work fork would
have done on the first page fault immediately, since it's easy to
argue that it's not much worse than we have now and much better in
many cases, and then try to experiment and figure out what the
correct solution is.
From: [EMAIL PROTECTED]
These patches make page tables relocatable for numa, memory
defragmentation, and memory hotplug. The need to rewalk the page
tables before making any changes causes a 3.5% performance degredation
in the lmbench page miss micro benchmark. Please check the linux-mm
list arc
---
diff -uprwNbB -X 2.6.23/Documentation/dontdiff
2.6.23/arch/i386/mm/hugetlbpage.c 2.6.23a/arch/i386/mm/hugetlbpage.c
--- 2.6.23/arch/i386/mm/hugetlbpage.c 2007-10-09 13:31:38.0 -0700
+++ 2.6.23a/arch/i386/mm/hugetlbpage.c 2007-10-29 09:48:48.0 -0700
@@ -87,6 +87,7 @@ static
gured out how to reduce the 3.5% page
fault overhead to almost nothing.
Ross
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
I have an app with a small fixed memory footprint that does a lot of
random reads from a large file. I thought if I added more memory to
the machine the VM would do more caching of the disk, but added memory
does not seem to make any difference. I played with some of the params
in /proc/sys/vm and
't
be in the near future), then there is no point in turning interrupts
on and off at all.
Ross
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
iguration.
So, if you're getting a connected route for 10.3.0.0/16 out of dev
eth0, it's because you assigned some IP in that subnet to that device,
with a netmask of 255.255.0.0
Check that your netmask is correct.
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should
Hi all,
I'm trying to track down whats causing the problems with a Silicon Image
3124 PCI/PCI-X sata card and running it under linux.
A quick rundown on the hardware that is in use.
Athlon X2 4200+
Asus A8S-X Mobo
Silicon Image 3124 4port SATA RAID card (using a PCI slot)
5x500gb WDJB 500gb SATA
What would you define a media error as though? I mean my first thought
is a bad block, but a scan of the disc doesn't report anything like
that. It also seems to be intermittent, however recently it has been
reproducible.
- Ross
Jeff Garzik wrote:
> Ross Fawcett wrote:
>> The er
on't use that on my D820.
I have a D820 and I had a horrible time with the wireless for a long
time. Every five minutes or so, the card would flip out and burn 100%
CPU making the box unusable for 15-45 seconds.
The most recent version of the firmware fixed this issue and now
things are much
ded at system boot, hald or
udev may be doing something with it.
When you loaded it manually, you didn't have udev rescan for devices
so they didn't notice that you had loaded up a new disk.
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematician
0MiB/sec.
I'm using kernel 2.6.18-4-686 from debian. Any ideas on what's
slowing down dump?
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematicians, and all those who
make empty prophecies. The danger already exists that the mathematicians
hav
only recently
has it been causing the kernel to crash. I know this is avoidable by
using cdda2wav in raw mode but it would be good to fix.
If anybody has any pointers about how I should go about this it would be
most appriciated.
Many thanks,
Ross
Ross Alexander
Phone: +44 20 8752 3394
SAP
the call trace isn't identical. Lastest says "kernel BUG at
kernel/timer.c:551! invalid opcode: [1] PREMPT KERNEL". I can run
this again if necessary.
Cheers,
Ross
Unable gto handle kernel NULL pointer dereferenced at
RIP: [<>]
locking */
#define RADIX_DAX_ENTRY_LOCK (1 << RADIX_TREE_EXCEPTIONAL_SHIFT)
This locking code was also made specific to the DAX code instead of being
generally implemented in radix-tree.h.
So, fix the comment.
Signed-off-by: Ross Zwisler
---
include/linux/radix-tree.h | 2 +-
1 file changed, 1 inserti
On Tue, Aug 23, 2016 at 04:04:11PM -0600, Ross Zwisler wrote:
> Currently when doing a DAX hole punch with ext4 we fail to do a writeback.
> This is because the logic around filemap_write_and_wait_range() in
> ext4_punch_hole() only looks for dirty page cache pages in the radix tree,
Currently when doing a DAX hole punch with ext4 we fail to do a writeback.
This is because the logic around filemap_write_and_wait_range() in
ext4_punch_hole() only looks for dirty page cache pages in the radix tree,
not for dirty DAX exceptional entries.
Signed-off-by: Ross Zwisler
Reviewed-by
The global 'wait_table' variable is only used within fs/dax.c, and
generates the following sparse warning:
fs/dax.c:39:19: warning: symbol 'wait_table' was not declared. Should it be
static?
Make it static so it has scope local to fs/dax.c, and to make sparse happy.
Signed-
can insert the 2MiB
entry. We can solve this problem if we need to, but I think that the cases
where both 2MiB entries and 4K entries are being used for the same range
will be rare enough and the gain small enough that it probably won't be
worth the complexity.
Signed-off-by: Ross Zwisle
inux/kernel/git/zwisler/linux.git/log/?h=dax_pmd_v3
Ross Zwisler (11):
ext4: allow DAX writeback for hole punch
ext4: tell DAX the size of allocation holes
dax: remove buffer_size_valid()
ext2: remove support for DAX PMD faults
dax: make 'wait_table' global variable static
dax
Now that DAX PMD faults are once again working and are now participating in
DAX's radix tree locking scheme, allow their config option to be enabled.
Signed-off-by: Ross Zwisler
---
fs/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/Kconfig b/fs/Kconfig
index 2bc7ad7..b6
No functional change.
Consistently use the variable name 'entry' instead of 'ret' for DAX radix
tree entries. This was already happening in most of the code, so update
get_unlocked_mapping_entry(), grab_mapping_entry() and
dax_unlock_mapping_entry().
Signed-off-by: Ross Zw
dax_pmd_fault() is the old struct buffer_head + get_block_t based 2 MiB DAX
fault handler. This fault handler has been disabled for several kernel
releases, and support for PMDs will be reintroduced using the struct iomap
interface instead.
Signed-off-by: Ross Zwisler
---
fs/dax.c
he same bit lock.
To accomplish this, for ranges covered by a PMD entry we will instead lock
based on the page offset of the beginning of the PMD entry. The 'mapping'
pointer is still used in the same way.
Signed-off-by: Ross Zwisler
---
fs/dax.c| 37
Switch xfs_filemap_pmd_fault() from using dax_pmd_fault() to the new and
improved iomap_dax_pmd_fault(). Also, now that it has no more users,
remove xfs_get_blocks_dax_fault().
Signed-off-by: Ross Zwisler
---
fs/xfs/xfs_aops.c | 25 +
fs/xfs/xfs_aops.h | 3 ---
fs/xfs
#x27;t reliably get PMDs, remove support so that we don't have an
untested code path that we may someday traverse when we happen to get an
aligned block allocation. This should also make 4k DAX faults in ext2 a
bit faster since they will no longer have to call the PMD fault handler
only to get a res
Now that ext4 properly sets bh.b_size when we call get_block() for a hole,
rely on that value and remove the buffer_size_valid() sanity check.
Signed-off-by: Ross Zwisler
Reviewed-by: Jan Kara
---
fs/dax.c | 22 +-
1 file changed, 1 insertion(+), 21 deletions(-)
diff --git
can remove buffer_size_valid() in a later patch.
Signed-off-by: Ross Zwisler
Reviewed-by: Jan Kara
---
fs/ext4/inode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 0900cb4..9075fac 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -759,6 +759,9 @@
is config option was
introduced in this commit:
commit 03cdadb04077 ("block: disable block device DAX by default")
This change reverts that commit, removing the dead config option.
Signed-off-by: Ross Zwisler
Cc: Dave Hansen
Cc: Dan Williams
---
block/Kconfig | 13 -
fs/b
erved bits need to be masked off, and
the driver must avoid checking the state of those bits.
This change ensures that for hardware implementations that set these
reserved bits in the status register, the driver won't incorrectly fail the
block I/Os.
Signed-off-by: Ross Zwisler
Cc: D
On Tue, Sep 06, 2016 at 05:06:20PM +0200, Jan Kara wrote:
> On Thu 01-09-16 20:57:38, Ross Zwisler wrote:
> > On Wed, Aug 31, 2016 at 04:44:47PM +0800, Xiao Guangrong wrote:
> > > On 08/31/2016 01:09 AM, Dan Williams wrote:
> > > >
> > > > Can you post yo
On Wed, Sep 07, 2016 at 09:32:36PM -0700, Dan Williams wrote:
> [ adding linux-fsdevel and linux-nvdimm ]
>
> On Wed, Sep 7, 2016 at 8:36 PM, Xiao Guangrong
> wrote:
> [..]
> > However, it is not easy to handle the case that the new VMA overlays with
> > the old VMA
> > already got by userspace.
On Tue, Sep 13, 2016 at 06:38:02AM -0700, Dan Williams wrote:
> On Mon, Sep 12, 2016 at 11:01 PM, ryan chen wrote:
> > On Tue, Sep 13, 2016 at 10:50 AM, Dan Williams
> > wrote:
> >> On Mon, Sep 12, 2016 at 7:30 PM, ryan chen wrote:
> >>> Hi all,
> >>> Recently I'm trying to check the testing su
On Tue, Aug 23, 2016 at 04:04:12PM -0600, Ross Zwisler wrote:
> When DAX calls ext2_get_block() and the file offset points to a hole we
> currently don't set bh_result->b_size. When we re-enable PMD faults DAX
> will need bh_result->b_size to tell it the size of the hol
or lahf_lm
Another thing to do would be to run your test on bare metal on the same
machine and see if you get different results.
Thanks,
- Ross
On Wed, Aug 31, 2016 at 08:20:48PM +, Kani, Toshimitsu wrote:
> On Tue, 2016-08-30 at 17:01 -0600, Ross Zwisler wrote:
> > On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote:
> > >
> > > DAX PMDs have been disabled since Jan Kara introduced DAX radix
>
On Wed, Aug 31, 2016 at 10:08:59PM +, Kani, Toshimitsu wrote:
> On Wed, 2016-08-31 at 15:36 -0600, Ross Zwisler wrote:
> > On Wed, Aug 31, 2016 at 08:20:48PM +, Kani, Toshimitsu wrote:
> > >
> > > On Tue, 2016-08-30 at 17:01 -0600, Ross Zwisler wrote:
> >
On Wed, Aug 31, 2016 at 04:44:47PM +0800, Xiao Guangrong wrote:
> On 08/31/2016 01:09 AM, Dan Williams wrote:
> >
> > Can you post your exact reproduction steps? This test is not failing for
> > me.
> >
>
> Sure.
>
> 1. make the guest kernel based on your tree, the top commit is
>10d7902f
The pthread_mutex_t in regression1.c wasn't being initialized properly.
Signed-off-by: Ross Zwisler
---
tools/testing/radix-tree/regression1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/radix-tree/regression1.c
b/tools/testing/radix-tree/regressi
radix_tree_iter_next() zeros out iter->tags, so we end up exiting
radix_tree_next_slot() here:
if (flags & RADIX_TREE_ITER_TAGGED) {
void *canon = slot;
iter->tags >>= 1;
if (unlikely(!iter->tags))
return NULL;
Signed
ot'.
4) radix_tree_iter_next() via tagged iteration like
radix_tree_for_each_tagged(). This happens in shmem_wait_for_pins().
radix_tree_iter_next() zeros out iter->tags, so we end up exiting
radix_tree_next_slot() here:
if (flags & RADIX_TREE_ITER_TAGGED) {
void *canon = slot;
On Tue, Aug 02, 2016 at 12:26:53PM -0600, Ross Zwisler wrote:
> The "NVDIMM Block Window Driver Writer's Guide":
>
> http://pmem.io/documents/
> http://pmem.io/documents/NVDIMM_DriverWritersGuide-July-2016.pdf
>
> defines the layout of the block window st
oblem if we need to, but I think that the cases
where both 2MiB entries and 4K entries are being used for the same range
will be rare enough and the gain small enough that it probably won't be
worth the complexity.
Signed-off-by: Ross Zwisler
---
fs/dax.c
Now that DAX PMD faults are once again working and are now participating in
DAX's radix tree locking scheme, allow their config option to be enabled.
Signed-off-by: Ross Zwisler
---
fs/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/Kconfig b/fs/Kconfig
index 2bc7ad7..b6
The global 'wait_table' variable is only used within fs/dax.c, and
generates the following sparse warning:
fs/dax.c:39:19: warning: symbol 'wait_table' was not declared. Should it be
static?
Make it static so it has scope local to fs/dax.c, and to make sparse happy.
Signed-
holes in ext2_get_block().
(Jan)
- Made the 'wait_table' global variable static in respnse to a sparse
warning.
- Fixed some more inconsitent usage between the names 'ret' and 'entry'
for radix tree entry variables.
Ross Zwisler (9):
ext4: allow DAX writeba
No functional change.
Consistently use the variable name 'entry' instead of 'ret' for DAX radix
tree entries. This was already happening in most of the code, so update
get_unlocked_mapping_entry(), grab_mapping_entry() and
dax_unlock_mapping_entry().
Signed-off-by: Ross Zw
gned-off-by: Ross Zwisler
---
fs/ext2/inode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c
index d5c7d09..dd55d74 100644
--- a/fs/ext2/inode.c
+++ b/fs/ext2/inode.c
@@ -773,6 +773,9 @@ int ext2_get_block(struct inode *inode, sector_t iblock,
struct buffe
k() has the hole size information from ext4_map_blocks(), so
populate bh->b_size.
Signed-off-by: Ross Zwisler
Reviewed-by: Jan Kara
---
fs/ext4/inode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 0900cb4..9075fac 100644
--- a/fs/ext4/inode.c
he same bit lock.
To accomplish this, for ranges covered by a PMD entry we will instead lock
based on the page offset of the beginning of the PMD entry. The 'mapping'
pointer is still used in the same way.
Signed-off-by: Ross Zwisler
---
fs/dax.c| 37
Currently when doing a DAX hole punch with ext4 we fail to do a writeback.
This is because the logic around filemap_write_and_wait_range() in
ext4_punch_hole() only looks for dirty page cache pages in the radix tree,
not for dirty DAX exceptional entries.
Signed-off-by: Ross Zwisler
Reviewed-by
Now that all our supported filesystems (ext2, ext4 and XFS) all properly
set bh.b_size when we call get_block() for a hole, rely on that value and
remove the buffer_size_valid() sanity check.
Signed-off-by: Ross Zwisler
Reviewed-by: Jan Kara
---
fs/dax.c | 22 +-
1 file
don't do any work.
Signed-off-by: Ross Zwisler
Reported-by: Jeff Moyer
Cc: sta...@vger.kernel.org
---
mm/readahead.c | 4
1 file changed, 4 insertions(+)
diff --git a/mm/readahead.c b/mm/readahead.c
index 65ec288..a9ba1be 100644
--- a/mm/readahead.c
+++ b/mm/readahead.c
@@ -8,6 +
don't do any work.
Signed-off-by: Ross Zwisler
Reported-by: Jeff Moyer
---
Changes from v1:
- Added a comment so readers don't have to go putzing around in the git
tree to understand why we're doing what we're doing. :) (akpm)
---
mm/readahead.c | 9 +
1 file cha
don't do any work.
Signed-off-by: Ross Zwisler
Reported-by: Jeff Moyer
Cc: [4.5+]
---
Changes from v1:
- Added a comment so readers don't have to go putzing around in the git
tree to understand why we're doing what we're doing. :) (akpm)
- Resending, adding sta...@vger
On Thu, Aug 25, 2016 at 12:57:28AM -0700, Christoph Hellwig wrote:
> Hi Ross,
>
> can you take at my (fully working, but not fully cleaned up) version
> of the iomap based DAX code here:
>
> http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/iomap-dax
>
>
arbitrary kernel addresses with this path.
Signed-off-by: Ross Zwisler
---
Adding a comment instead of adding redundant access_ok() calls in the DAX
code. If this is the wrong path to take, please let me know.
fs/dax.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/fs/dax.c b/fs/dax.c
On Thu, Aug 17, 2017 at 10:53:32AM +0200, Jan Kara wrote:
> On Wed 16-08-17 11:36:15, Ross Zwisler wrote:
> > Add a comment explaining how the user addresses provided to read(2) and
> > write(2) are validated in the DAX I/O path. We call dax_copy_from_iter()
> > or copy_to_it
On Mon, Jun 19, 2017 at 10:22:14PM -0700, Darrick J. Wong wrote:
<>
> Fourth, the VFS entry points for things like read, write, truncate,
> utimes, fallocate, etc. all just bail out if S_IOMAP_FROZEN is set on a
> file, so that the block map cannot be modified. mmap is still allowed,
> as we've di
the fault handlers and just retry.
Signed-off-by: Ross Zwisler
Cc: sta...@vger.kernel.org
---
For both the -mm tree and for stable, feel free to squash this with the
original commit if you think that is appropriate.
This has passed targeted testing and an xfstests run.
---
fs/dax.c | 11 +++---
d since v1:
> - rename to device private memory (from device unaddressable)
>
> Signed-off-by: Jérôme Glisse
> Acked-by: Dan Williams
> Cc: Ross Zwisler
> ---
<>
> @@ -35,18 +37,88 @@ static inline struct vmem_altmap *to_vmem_altmap(unsigned
On Tue, Oct 24, 2017 at 03:22:23PM -0400, Mike Snitzer wrote:
> On Fri, Oct 20 2017 at 1:24am -0400,
> Ross Zwisler wrote:
>
> > Now that we have the ability log filesystem writes using a flat buffer, add
> > support for DAX. Unfortunately we can't easily track data
On Wed, Oct 25, 2017 at 03:19:22PM +0300, Amir Goldstein wrote:
> On Sun, Oct 22, 2017 at 9:56 AM, Amir Goldstein wrote:
> > On Sat, Oct 21, 2017 at 12:25 AM, Ross Zwisler
> > wrote:
> >> Add a test that exercises DAX's new MAP_SYNC flag.
> >>
> >>
at we write via the
mmap(), so we can't do any data integrity checking. We can only verify
that the metadata writes for the page faults happened.
Signed-off-by: Ross Zwisler
---
Changes since v2:
- Fixed _require_log_writes() so that DAX will be disallowed if the
version of the dm-log-wr
1 - 100 of 1375 matches
Mail list logo
