Skip to contentSkip to conversation

I'd like to attend ;)

Lsf10-pc Ric Wheeler 5 participants 7 messages Mar 1, 2010 – Jun 17, 2010 1 message not in the archive VFS

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 10 lines · Eric Sandeen

I still need to decide which specific topic to bring/promote, but I'd certainly like to attend, as I have in the past.

Generally would like to talk about...

Trim/discard plans in filesystem - lately I'm thinking a batch mechanism may be better than trim-as-you-go.

Advancements in generic test infrastructures since last year.

Quoted 8 lines

Could talk a bit about the advancements in proper alignment detection& setup for storage& filesystems but that's not a very big topic.

Jan's suggestion of some writeback sanity sounds good to me too.

Thanks,
-Eric

I think that all of the above are great topics for this time around.

Specifically, the alignment work has been interesting in that we have tried to get not just the kernel bits but the entire stack to work properly.

Both this and the discard work should still be quite topical if we can get the various storage vendors to evaluate our current upstream bits in time :-)

ric

#2 lore raw
Quoted 11 lines · Ric Wheeler
Quoted 10 lines · Eric Sandeen

I still need to decide which specific topic to bring/promote, but I'd certainly
like to attend, as I have in the past.

Generally would like to talk about...

Trim/discard plans in filesystem - lately I'm thinking a batch mechanism may
be better than trim-as-you-go.

Quoted 6 lines
Quoted 6 lines

Advancements in generic test infrastructures since last year.

Could talk a bit about the advancements in proper alignment detection& setup for storage& filesystems but that's not a very big topic.

Jan's suggestion of some writeback sanity sounds good to me too.

Why just sanity. We can also talk about the new cache writeback techniques FS metadata specific as well as application dirty pages to improve performance
of large sequential write NFS workloads.

Quoted 24 lines
Quoted 4 lines

Thanks,
-Eric

I think that all of the above are great topics for this time around.

Specifically, the alignment work has been interesting in that we have tried to get not just the kernel bits but the entire stack to work properly.

Both this and the discard work should still be quite topical if we can get the various storage vendors to evaluate our current upstream bits in time :-)

ric

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 15 lines
Best Regards
Sorin Faibish
Corporate Distinguished Engineer
Network Storage Group

        EMC²
where information lives

Phone: 508-435-1000 x 48545
Cellphone: 617-510-0422
Email : [email protected]
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
In reply to Ric Wheeler
Quoted 22 lines · Ric Wheeler
Quoted 10 lines · Eric Sandeen

I still need to decide which specific topic to bring/promote, but I'd certainly like to attend, as I have in the past.

Generally would like to talk about...

Trim/discard plans in filesystem - lately I'm thinking a batch mechanism may be better than trim-as-you-go.

Advancements in generic test infrastructures since last year.

Quoted 8 lines

Could talk a bit about the advancements in proper alignment detection& setup for storage& filesystems but that's not a very big topic.

Jan's suggestion of some writeback sanity sounds good to me too.

Thanks,
-Eric

I think that all of the above are great topics for this time around.

Quoted 7 lines

Specifically, the alignment work has been interesting in that we have tried to get not just the kernel bits but the entire stack to work properly.

Both this and the discard work should still be quite topical if we can get the various storage vendors to evaluate our current upstream bits in time :-)

As you know, I've been picking away at the discard support from the file system all the way down to the storage. I think I should have some good numbers and guidance come time for the workshop.

I am also interested in discussing all things I/O scheduler.

Oh, and I'd like to attend as well. ;)

-Jeff

#4 lore raw
Quoted 38 lines · Jeff Moyer
Quoted 23 lines · Ric Wheeler
Quoted 10 lines · Eric Sandeen

I still need to decide which specific topic to bring/promote, but I'd certainly like to attend, as I have in the past.

Generally would like to talk about...

Trim/discard plans in filesystem - lately I'm thinking a batch mechanism may be better than trim-as-you-go.

Advancements in generic test infrastructures since last year.

Quoted 9 lines

Could talk a bit about the advancements in proper alignment detection&
setup for storage& filesystems but that's not a very big topic.

Jan's suggestion of some writeback sanity sounds good to me too.

Thanks,
-Eric

I think that all of the above are great topics for this time around.

Quoted 8 lines

Specifically, the alignment work has been interesting in that we have tried to get not just the kernel bits but the entire stack to work properly.

Both this and the discard work should still be quite topical if we can get the various storage vendors to evaluate our current upstream bits in time :-)

As you know, I've been picking away at the discard support from the file system all the way down to the storage. I think I should have some good numbers and guidance come time for the workshop.

Quoted 6 lines

I am also interested in discussing all things I/O scheduler.

Oh, and I'd like to attend as well. ;)

-Jeff

One topic that I think that might be interesting is to talk about how well we did integrating all of these new features into the stack that cross IO/FS/scheduler boundaries. In a way, we got ahead of the hardware vendors with both the discard support and the various topology bits but did manage to get that supported not just in the kernel but up the tool chain as well.

Might be interesting to see where we ended up, think about next steps and if/how we would improve on what we have....

ric

#5 lore raw
Quoted 53 lines · Ric Wheeler
Quoted 45 lines · Jeff Moyer
Quoted 28 lines · Ric Wheeler
Quoted 13 lines · Eric Sandeen

I still need to decide which specific topic to bring/promote, but I'd certainly
like to attend, as I have in the past.

Generally would like to talk about...

Trim/discard plans in filesystem - lately I'm thinking a batch mechanism may
be better than trim-as-you-go.

Advancements in generic test infrastructures since last year.

Quoted 9 lines

Could talk a bit about the advancements in proper alignment detection& setup for storage&   filesystems but that's not a very big topic.

Jan's suggestion of some writeback sanity sounds good to me too.

Thanks,
-Eric

I think that all of the above are great topics for this time around.

Quoted 8 lines

Specifically, the alignment work has been interesting in that we have tried to get not just the kernel bits but the entire stack to work properly.

Both this and the discard work should still be quite topical if we can get the various storage vendors to evaluate our current upstream bits in time :-)

As you know, I've been picking away at the discard support from the file system all the way down to the storage.  I think I should have some good numbers and guidance come time for the workshop.

Quoted 6 lines

I am also interested in discussing all things I/O scheduler.

Oh, and I'd like to attend as well.  ;)

-Jeff

Quoted 8 lines

One topic that I think that might be interesting is to talk about how well we did integrating all of these new features into the stack that cross IO/FS/scheduler boundaries. In a way, we got ahead of the hardware vendors with both the discard support and the various topology bits but did manage to get that supported not just in the kernel but up the tool chain as well.

Might be interesting to see where we ended up, think about next steps and if/how we would improve on what we have....

I would like attend this year's LSF.

I helped implement and coordinate the development of the I/O Topology support through the entire storage stack. My specific contribution was in DM and LVM2 but I also worked with Martin Petersen and the developers of the layers above the block layer (partition tools, filesystems, virtio+qemu).

I'm now looking to implement comprehensive discard support for DM. There is a need for various discard support changes in the block layer (and below) so it'd be interesting if we touched on this. But my hope is that at least some patches will make their way upstream before LSF (for 2.6.36 inclusion) -- e.g.: hch's patches to push a discard's payload allocation down to the LLD (SCSI or ATA).

I'll also be prepared to discuss aspects of DM if there is any interest.

Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#6 lore raw
Quoted 79 lines · Mike Snitzer
Quoted 53 lines · Ric Wheeler
Quoted 44 lines · Jeff Moyer
Quoted 27 lines · Ric Wheeler
Quoted 12 lines · Eric Sandeen

I still need to decide which specific topic to bring/promote, but I'd certainly
like to attend, as I have in the past.

Generally would like to talk about...

Trim/discard plans in filesystem - lately I'm thinking a batch mechanism may
be better than trim-as-you-go.

Advancements in generic test infrastructures since last year.

Quoted 10 lines

Could talk a bit about the advancements in proper alignment detection&
setup for storage& filesystems but that's not a very big topic.

Jan's suggestion of some writeback sanity sounds good to me too.

Thanks,
-Eric

I think that all of the above are great topics for this time around.

Quoted 9 lines

Specifically, the alignment work has been interesting in that we have tried to get not just the kernel bits but the entire stack to work properly.

Both this and the discard work should still be quite topical if we can get the various storage vendors to evaluate our current upstream bits in time :-)

As you know, I've been picking away at the discard support from the file system all the way down to the storage. I think I should have some good numbers and guidance come time for the workshop.

Quoted 7 lines

I am also interested in discussing all things I/O scheduler.

Oh, and I'd like to attend as well. ;)

-Jeff

Quoted 9 lines

One topic that I think that might be interesting is to talk about how well we did integrating all of these new features into the stack that cross IO/FS/scheduler boundaries. In a way, we got ahead of the hardware vendors with both the discard support and the various topology bits but did manage to get that supported not just in the kernel but up the tool chain as well.

Might be interesting to see where we ended up, think about next steps and if/how we would improve on what we have....

I would like attend this year's LSF.

I helped implement and coordinate the development of the I/O Topology support through the entire storage stack. My specific contribution was in DM and LVM2 but I also worked with Martin Petersen and the developers of the layers above the block layer (partition tools, filesystems, virtio+qemu).

I'm now looking to implement comprehensive discard support for DM. There is a need for various discard support changes in the block layer (and below) so it'd be interesting if we touched on this. But my hope is that at least some patches will make their way upstream before LSF (for 2.6.36 inclusion) -- e.g.: hch's patches to push a discard's payload allocation down to the LLD (SCSI or ATA).

Quoted 4 lines

I'll also be prepared to discuss aspects of DM if there is any interest.

Mike

I think that these are all great topics - getting discard finished for DM will be an important goal for the coming year (especially given the huge surge in SSD devices that really, really can start to use this !!!)

ric

#7 lore raw
Quoted 80 lines · Ric Wheeler
Quoted 79 lines · Mike Snitzer
Quoted 53 lines · Ric Wheeler
Quoted 44 lines · Jeff Moyer
Quoted 27 lines · Ric Wheeler
Quoted 12 lines · Eric Sandeen

I still need to decide which specific topic to bring/promote, but I'd certainly
like to attend, as I have in the past.

Generally would like to talk about...

Trim/discard plans in filesystem - lately I'm thinking a batch mechanism may
be better than trim-as-you-go.

Advancements in generic test infrastructures since last year.

Quoted 10 lines

Could talk a bit about the advancements in proper alignment detection&
setup for storage& filesystems but that's not a very big topic.

Jan's suggestion of some writeback sanity sounds good to me too.

Thanks,
-Eric

I think that all of the above are great topics for this time around.

Quoted 9 lines

Specifically, the alignment work has been interesting in that we have tried to get not just the kernel bits but the entire stack to work properly.

Both this and the discard work should still be quite topical if we can get the various storage vendors to evaluate our current upstream bits in time :-)

As you know, I've been picking away at the discard support from the file system all the way down to the storage. I think I should have some good numbers and guidance come time for the workshop.

Quoted 7 lines

I am also interested in discussing all things I/O scheduler.

Oh, and I'd like to attend as well. ;)

-Jeff

Quoted 9 lines

One topic that I think that might be interesting is to talk about how well we did integrating all of these new features into the stack that cross IO/FS/scheduler boundaries. In a way, we got ahead of the hardware vendors with both the discard support and the various topology bits but did manage to get that supported not just in the kernel but up the tool chain as well.

Might be interesting to see where we ended up, think about next steps and if/how we would improve on what we have....

I would like attend this year's LSF.

I helped implement and coordinate the development of the I/O Topology support through the entire storage stack. My specific contribution was in DM and LVM2 but I also worked with Martin Petersen and the developers of the layers above the block layer (partition tools, filesystems, virtio+qemu).

I'm now looking to implement comprehensive discard support for DM. There is a need for various discard support changes in the block layer (and below) so it'd be interesting if we touched on this. But my hope is that at least some patches will make their way upstream before LSF (for 2.6.36 inclusion) -- e.g.: hch's patches to push a discard's payload allocation down to the LLD (SCSI or ATA).

Quoted 8 lines
Quoted 4 lines

I'll also be prepared to discuss aspects of DM if there is any interest.

Mike

I think that these are all great topics - getting discard finished for DM will be an important goal for the coming year (especially given the huge surge in SSD devices that really, really can start to use this !!!)

Just a procedural note: Since I'm compiling the list of attendee request list, replying to someone else's request is not such a good idea because I went by the thread heads when I did it ...

James