My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 68: Relocation Using Worker Threads
2 people starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  checkout...@gmail.com
Closed:  Mar 2009


 
Project Member Reported by checkout...@gmail.com, Mar 3, 2009
I have performed relocation using worker threads.
one file is successfully relocated.
but relocating more than one file holds a problem.

Iam still working on it ..
Mar 3, 2009
Project Member #1 sandeepksinha
I think trying it just for two inode numbers will give you an idea.
Try this and keep posted here.

Whats happening for two files?
One of the probelms that I see is that when the second process is picked from the 
worker thread, we start using the data structures of OHSM and now the problem is 
that if the first thread is still working. Both these threads will be working on the 
same data structures.
Mar 3, 2009
Project Member #2 sandeepksinha
I think trying it just for two inode numbers will give you an idea.
Try this and keep posted here.

Whats happening for two files?
One of the probelms that I see is that when the second process is picked from the 
worker thread, we start using the data structures of OHSM and now the problem is 
that if the first thread is still working. Both these threads will be working on the 
same data structures.
Mar 3, 2009
Project Member #3 checkout...@gmail.com
Hello Everyone ,

The Problem of work queue has been resolved and we can now relocate multiple files
successfully using worker threads.
Status: Review-Req
Labels: -Priority-Medium Priority-Low
Mar 3, 2009
Project Member #4 sandeepksinha
Wonderful work.

But according to my experiences I doubt your words.
Can you expalin me what exactly the problem was and how did you manager to find the 
problem ?

Whenever you open a new issue, you should always specify the problem statement and 
your approach that you intend to take.
Mar 4, 2009
Project Member #5 checkout...@gmail.com
Hello Sir,

The Problem Statement was to relocate files using worker threads.

The Problem faced was that it was relocating only one file.

But when i added flush_scheduled_work() it started to work fine .




Mar 4, 2009
Project Member #6 sandeepksinha
 Issue 28  has been merged into this issue.
Mar 4, 2009
Project Member #7 sandeepksinha
Do one thing take 1000 files for relocation without worker threads and then with the 
worker threads.
See, the time difference.

Also, can be split the job of scanning the FS into mutiple threads which will scan 
single BG and move it into the work queue.

I am sure, we will get significant performance gain here as well.
Mar 6, 2009
#8 postri...@gmail.com
The work is currently on hold due to ext3Yaan 
Status: On-Hold
Mar 7, 2009
Project Member #9 sandeepksinha
I think the basic worker thread part is already done here.
And that is a part of OHSM 1.0 Now.
So, this issue can be closed if it has been tested by vineet.

What I have mentioned here is some of the enhancement. Those will be handle through 
separate issues.
Mar 7, 2009
Project Member #10 checkout...@gmail.com
Hello Sir,

Yes the basic worker thread is working and is tested. 
So i am closing this issue.
Status: Done

Powered by Google Project Hosting