It is be possible to send the lock handle along with each read
or write request because the client is already doing a lock match itself so there isn't any reason the OST should have to re-do that search. b=15198 i=johann i=shadow
Showing
- lustre/ChangeLog 8 additions, 0 deletionslustre/ChangeLog
- lustre/include/lustre/lustre_idl.h 62 additions, 74 deletionslustre/include/lustre/lustre_idl.h
- lustre/include/obd.h 2 additions, 0 deletionslustre/include/obd.h
- lustre/lov/lov_obd.c 4 additions, 4 deletionslustre/lov/lov_obd.c
- lustre/mds/mds_lov.c 2 additions, 4 deletionslustre/mds/mds_lov.c
- lustre/obdclass/obdo.c 4 additions, 5 deletionslustre/obdclass/obdo.c
- lustre/obdecho/echo_client.c 2 additions, 2 deletionslustre/obdecho/echo_client.c
- lustre/obdfilter/filter.c 3 additions, 3 deletionslustre/obdfilter/filter.c
- lustre/obdfilter/filter_log.c 2 additions, 2 deletionslustre/obdfilter/filter_log.c
- lustre/osc/osc_request.c 11 additions, 7 deletionslustre/osc/osc_request.c
- lustre/ost/ost_handler.c 21 additions, 5 deletionslustre/ost/ost_handler.c
- lustre/ptlrpc/wiretest.c 28 additions, 7 deletionslustre/ptlrpc/wiretest.c
- lustre/utils/obdiolib.c 2 additions, 2 deletionslustre/utils/obdiolib.c
- lustre/utils/wirecheck.c 7 additions, 4 deletionslustre/utils/wirecheck.c
- lustre/utils/wiretest.c 28 additions, 7 deletionslustre/utils/wiretest.c
Loading
Please register or sign in to comment